Electronic device with enhanced method of displaying notifications

ABSTRACT

There is disclosed an electronic device comprising a receiver, a display, an application processor and a sensor hub. The receiver is configured to receive notifications from a remote device. The display is configured to provide information including notifications. The application processor and the sensor hub are in communication with the display. The application processor is configured to provide instructions for displaying full screen information at the display during a non-sleep mode of the electronic device. The full screen information includes a first notification associated with information received by the electronic device during the non-sleep mode. The sensor hub is configured to provide instructions for displaying partial screen information at the display during a sleep mode of the electronic device. The partial screen information includes a second notification associated with information received by the electronic device during the sleep mode.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of commonly assigned U.S. patentapplication Ser. No. 13/830,452, filed on Mar. 14, 2013, titled“Electronic Device With Enhanced Method of Displaying Notifications”;and U.S. patent application Ser. No. 13/836,987, filed on Mar. 15, 2013,titled “Electronic Device With Enhanced Method of DisplayingNotifications”; from which benefits under 35 USC §120 are hereby claimedand the contents of which are hereby incorporated by reference herein.Also, the present application is a non-provisional application ofcommonly assigned U.S. Provisional Patent Application No. 61/720,322,filed on Oct. 30, 2012; U.S. Provisional Patent Application No.61/736,536, filed on Dec. 12, 2012; and U.S. Provisional PatentApplication No. 61/757,690, filed on Jan. 28, 2013; from which benefitsunder 35 USC §119(e) are hereby claimed and the contents of which arehereby incorporated by reference herein.

FIELD OF THE INVENTION

The present invention relates generally to the field of electronicdevices having notification features to provide specialized informationto a user.

BACKGROUND OF THE INVENTION

The traditional “Notification LED” has lost its usefulness for anyonewho gets a constant stream of notifications. For such users, such Leedsare constantly blinking and become incessant “noise” that provide littlein the way of useful information and, indeed, an always-blinking LEDdrowns out important notifications. Additionally, devices employing suchLEDs foster an operational paradigm of “fidgeting” in which the usermust constantly wake the device simply to view the time or weed throughsuch notifications. Such operation is both time consuming andcognitively draining.

In view of such concerns, and others, it would be advantageous if one ormore improved methods of providing notifications to users of electronicdevices, and improved electronic devices configured to perform suchmethods, could be developed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view of an example embodiment of an electronicdevice in accordance with the present disclosure;

FIG. 2 is a block diagram representing example components of theelectronic device of FIG. 1;

FIG. 3, represented by FIGS. 3A and 3B, is a flow chart showing anexample process performed by the electronic device of FIGS. 1 and 2 inaccordance with one embodiment of the present disclosure;

FIGS. 4A, 4B, 4C, and 4D are four example views of a display screen ofthe electronic device of FIGS. 1 and 2 during four different points ofoperation in accordance with the example process of FIG. 3;

FIGS. 5A, 5B, 5C, and 5D respectively show the example views of FIGS.4A, 4B, 4C, and 4D of the display screen, respectively, in combinationwith illustrations of a user interacting with the display screen;

FIG. 6 is a modified flow chart illustrating, partly by way of a seriesof additional example views of the display screen of the electronicdevice of FIGS. 1 and 2, operation of the electronic device during abreathing mode portion of the process of FIG. 3;

FIG. 7 a graph illustrating example variation in brightness of thedisplay screen of the electronic device of FIGS. 1 and 2 duringoperation in the breathing mode portion of the example process of FIG. 3as illustrated by FIG. 6;

FIG. 8A is a view of an example of a full image in a frame buffer thatcan be displayed on the display screen of the electronic device at oneor more times during the example process of FIG. 3, and FIG. 8B is afurther view showing the full image of FIG. 8A additionally in relationto several example partial regions of the display screen;

FIG. 9, represented by FIGS. 9A and 9B, is a modified flow chartillustrating, partly by way of a series of additional example views ofthe display screen of the electronic device of FIGS. 1 and 2, operationof the electronic device as it transitions among the breathing modeportion of the process of FIG. 3 illustrated by FIG. 6, a non-breathingmode of that process, and a peek view mode of that process; and

FIGS. 10A and 10B are additional flow charts showing further examplesubprocesses that can be performed by the electronic device of FIGS. 1and 2, which can be considered to be encompassed generally by theexample process of FIG. 3.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The present inventors have recognized that a variety of enhancements canbe provided to electronic devices so as to enable to the electronicdevices to better provide notifications to users, and to the methods ofoperation of electronic devices in providing notifications. The presentinventors have further recognized that, although mobile device displaysand indeed the application processors of mobile devices are in apowered-down or “off” much or most of the time (e.g., in a “sleepmode”), so as to save on power consumed by such devices, such an “off”state of the display presents an opportunity for displaying the mostrelevant information at just the right time. Further, the presentinventors have recognized that, because attention is a limited resource,in addition to showing the right information at the right time,displaying of notifications in this manner during the “off” state couldalso help reduce the amount of time it takes to access the mostimportant notifications. By giving users the right amount of informationat the right time, the users will be better informed to decide whetheror not to pick up and actively use (unlock or turn “on”) their device—orto simply dismiss such notifications and never have to unlock theirdevice.

Additionally, the present inventors have also recognized that it ispossible to allow for ongoing actuation of a mobile device display, evenwhile the mobile device application processor and display aretechnically in a powered-down or “off” state, by implementing SmartPartial OLED display technology and a sensor hub (or other auxiliaryprocessing device) for controlling a display using such technology,rather than using mobile device application processor, so as to achievethe displaying of notifications in a low-power (or lower-power) mannerrelative to normal “on” state operation of a display by way of themobile device application processor. Embodiments operating in thismanner can be consider as providing “always-on” operation insofar as,even though the mobile device (or at least the mobile device applicationprocessor) is powered-down or off, the display can still be actuated todisplay notifications when appropriate. That is, touch inputs can bereceived, while the display is in a lower power state that is more akinto an “off” state in terms of power usage, insofar as the display is“on” only periodically or otherwise to a limited extent. Such operationcan be advantageous both in terms of reducing the rate of batterydepletion, as well as reducing the chance that portions of a displaymight be overly illuminated for too great of time in a manner that coulddamage the display.

In at least some embodiments, the display of the “right information atthe right time” is achieved by leveraging the Smart Partial OLED displaysystem to display an optimized set of notifications while the screen is“off”, where optimization can be achieved for example by way ofintelligent prioritization/ranking based on various information such asvarious inputs/behaviors, and improved notification management. In thismanner, the most important contextually-relevant information reaches theuser, and particularly can be provided to the user when the user has aneed for that information (in such cases, there can also be integrationwith personal assistant-type applications such as Google Now availablefrom Google, Inc. of Mountain View, Calif. or Siri available from Apple,Inc. of Cupertino, Calif.).

Also, in at least some embodiments, the “always-on” operation providesusers with a seamless or substantially seamless experience as the usersutilize the device and the device transitions between the “screen off”state (lock screen) and the “on” state. In at least some exampleembodiments, the device comes alive while still in the “off” mode (e.g.,where the application processor is still dormant) by showing incomingnotifications as they occur, by providing “breathing” alerts on thescreen without draining the battery, by coming alive when the device ispicked up off of a surface such as a table. Also, in some exampleembodiments, the providing of notifications is entirely disabled by thedevice when the device recognizes a circumstance where the providing ofnotifications is inappropriate (e.g., when the device is face down, whenthe device is in a pocket, when it is nighttime, etc.).

Further, in at least some embodiments, the low-power operatingcapability of the OLED display during the “off” state of the device isfurther leveraged by operating the display in a manner by whichimportant notifications are shown only on a small part of the screen. Insome cases, not only does the display system display an optimized set ofnotifications while the screen is “off”, without significantly impactingbattery lift, but also the system allows for a select set of userinteractions during this state, which also for avoiding significantimpacts upon battery life. Also, in at least some cases, there canfurther be a continuous, cohesive experience between phone and watchoperation. Also, at least some embodiments can provide a user-centricapproach to security.

In view of the above, in at least some embodiments, the presentdisclosure relates to an electronic device including a receiver, adisplay, an application processor and a sensor hub. The receiver isconfigured to receive notifications from a remote device. The display isconfigured to provide information including notifications. Theapplication processor and the sensor hub are in communication with thedisplay. The application processor is configured to provide instructionsfor displaying full screen information at the display during a non-sleepmode of the electronic device. The full screen information includes afirst notification associated with first information received by theelectronic device during the non-sleep mode. The sensor hub isconfigured to provide instructions for displaying partial screeninformation at the display during a sleep mode of the electronic device.The partial screen information includes a second notification associatedwith second information received by the electronic device during thesleep mode.

Also, in at least some additional embodiments, the present disclosurerelates to a method of operating an electronic device so as to providenotifications. Full screen information is provided at a display of theelectronic device in response to instructions from an applicationprocessor during a non-sleep mode of the electronic device. The fullscreen information includes a first notification associated with firstinformation received by the electronic device during the non-sleep mode.Also, partial screen information is provided at the display in responseto instructions from a sensor hub during a sleep mode of the electronicdevice. The partial screen information includes a second notificationassociated with second information received by the electronic deviceduring the sleep mode.

Additionally, in at least some embodiments, the present disclosurerelates to a method of an electronic device for providing notifications.The method includes operating the electronic device in a higher-powermode of operation during which at least one application processor isactive in controlling displaying by a display of the electronic device,and receiving a first notification. The method also includes determiningthat the first notification satisfies at least one criterion for displayin a low-power mode of operation, and transitioning from thehigher-power mode of operation to a lower-power mode of operation duringwhich a sensor hub operates to provide at least one control signal tothe display. The method further includes actuating the display, inresponse to at least one control signal received from the sensor hub, sothat a first image portion identical to or based at least in part uponthe first notification is displayed in a periodic manner in which atfirst times the displayed first image portion is displayed with at leastone higher level of brightness and at second times the display firstimage portion is displayed with at least one lower level of brightness.The method also includes receiving a signal indicative of a user inputcorresponding to the first image portion, and taking at least one firstaction in response to the receiving of the signal.

Referring now to FIG. 1, there is illustrated a perspective view of anexample electronic device 100. In the present embodiment, the electronicdevice 100 can be any type of device capable of providing touch screeninteractive capabilities. Examples of the electronic device 100 include,but are not limited to, mobile devices, wireless devices, smart phones,tablet computing devices, personal digital assistants, personalnavigation devices, touch screen input device, touch or pen-based inputdevices, portable video and/or audio players, as well as any of avariety of other electronic devices. It is to be understood that theelectronic device 100 may take the form of a variety of form factors,such as, but not limited to, bar, tablet, flip/clam, slider and rotatorform factors.

In the present example embodiment shown in FIG. 1, the electronic device100 has a housing 101 comprising a front surface 103 which includes atouch screen display (that is a visible display) 105 that, together withcertain other features discussed below, constitutes a user interface. Inthe present example, the touch screen display 105 is a touch screenincluding a touch-sensitive surface that overlays a display surfaceforming part of (or that is positioned just underneath or inwardly of)the front surface 103. In the present embodiment, the touch screendisplay 105 (and particularly the display surface thereof) employsorganic light-emitting diode (OLED) technology. Further, the userinterface of the electronic device 100 as shown can also include one ormore input keys 107. Examples of the input key or keys 107 include, butare not limited to, keys of an alpha or numeric (e.g., alphanumeric)keypad (or other keyboard), physical keys, touch-sensitive surfaces,mechanical surfaces, multipoint directional keys, and side buttons orkeys. Further as shown, the electronic device 100 can also compriseapertures 109, 111 for audio output and input along the front surface103 (or other outer surfaces of the device).

Notwithstanding the particular features shown in FIG. 1, in an alternateembodiment, the electronic device can include other features. Forexample, in place of the touch screen display, in an alternateembodiment the electronic device can employ a touch-sensitive surfacesupported by the housing 101 that does not overlay (or is not overlaidby) any type of display. Indeed, although FIG. 1 shows particularlyexample display and user interface features, it is to be understood thatthe electronic device 100 can include a variety of other combinations ofdisplay and user interface features depending upon the embodiment.

Additionally as shown in FIG. 1, the electronic device 100 includes oneor more sensors 113, a number of which are shown to be positioned at orwithin an exterior boundary of the housing 101 (and can be supported onor within the housing 101). More particularly, as illustrated by FIG. 1,in the present embodiment the sensor or sensors 113 can be positioned atthe front surface 103 and/or another surface (such as one or more sidesurfaces 115) of the exterior boundary of the housing 101. In thepresent embodiment, at least some of the sensors 113 (whether at theexterior boundary or within the exterior boundary, i.e., internal to thehousing) are configured to detect one or more predeterminedenvironmental conditions associated with an environment external orinternal to the housing. Further examples of the sensors 113 aredescribed below in reference to FIG. 2.

Referring to FIG. 2, there is shown a block diagram representing examplecomponents (e.g., internal components) 200 of the electronic device 100of FIG. 1. In the present embodiment, the components 200 include one ormore wireless transceivers 201, one or more processors 203, one or morememories 205, one or more output components 207, and one or more inputcomponents 209. As already noted above, the electronic device 100includes a user interface, including the touch screen display 105, thatcomprises one or more of the output components 207 and one or more ofthe input components 209. Also as already discussed above, theelectronic device 100 includes a plurality of the sensors 113, severalof which are described in more detail below. In the present embodiment,the sensors 113 are in communication with (so as to provide sensorsignals to or receive control signals from) a sensor hub 223.

Further, the components 200 further include a device interface 215 toprovide a direct connection to auxiliary components or accessories foradditional or enhanced functionality. In addition, the internalcomponents 200 preferably include a power source or supply 217, such asa portable battery, for providing power to the other internal componentsand allow portability of the electronic device 100. As shown, all of thecomponents 200, and particularly the wireless transceivers 201,processors 203, memories 205, output components 207, input components209, sensor hub 223, device interface 215, and power supply 217, arecoupled directly or indirectly with one another by way of one or moreinternal communication link(s) 218 (e.g., an internal communicationsbus).

Further, in the present embodiment of FIG. 2, the wireless transceivers201 particularly include a cellular transceiver 211 and a Wi-Fitransceiver 213. Although in the present embodiment the wirelesstransceivers 201 particularly include two of the wireless transceivers203 and 205, the present disclosure is intended to encompass numerousembodiments in which any arbitrary number of (e.g., more than two)wireless transceivers employing any arbitrary number of (e.g., two ormore) communication technologies are present. More particularly, in thepresent embodiment, the cellular transceiver 211 is configured toconduct cellular communications, such as 3G, 4G, 4G-LTE, vis-à-vis celltowers (not shown), albeit in other embodiments, the cellulartransceiver 211 can be configured to utilize any of a variety of othercellular-based communication technologies such as analog communications(using AMPS), digital communications (using CDMA, TDMA, GSM, iDEN, GPRS,EDGE, etc.), and/or next generation communications (using UMTS, WCDMA,LTE, IEEE 802.16, etc.) or variants thereof.

By contrast, the Wi-Fi transceiver 213 is a wireless local area network(WLAN) transceiver configured to conduct Wi-Fi communications inaccordance with the IEEE 802.11(a, b, g, or n) standard with accesspoints. In other embodiments, the Wi-Fi transceiver 213 can instead (orin addition) conduct other types of communications commonly understoodas being encompassed within Wi-Fi communications such as some types ofpeer-to-peer (e.g., Wi-Fi Peer-to-Peer) communications. Further, inother embodiments, the Wi-Fi transceiver 213 can be replaced orsupplemented with one or more other wireless transceivers configured fornon-cellular wireless communications including, for example, wirelesstransceivers employing ad hoc communication technologies such as HomeRF(radio frequency), Home Node B (3G femtocell), Bluetooth and/or otherwireless communication technologies such as infrared technology.Although in the present embodiment each of the wireless transceivers 201serves as or includes both a respective transmitter and a respectivereceiver, it should be appreciated that the wireless transceivers arealso intended to encompass one or more receiver(s) that are distinctfrom any transmitter(s), as well as one or more transmitter(s) that aredistinct from any receiver(s). In one example embodiment encompassedherein, the wireless transceiver 201 include at least one receiver thatis a baseband receiver.

Exemplary operation of the wireless transceivers 201 in conjunction withothers of the components 200 of the electronic device 100 can take avariety of forms and can include, for example, operation in which, uponreception of wireless signals (as provided, for example, by remotedevice(s)), the internal components detect communication signals and thetransceivers 201 demodulate the communication signals to recoverincoming information, such as voice and/or data, transmitted by thewireless signals. After receiving the incoming information from thetransceivers 201, the processors 203 format the incoming information forthe one or more output components 207. Likewise, for transmission ofwireless signals, the processors 203 format outgoing information, whichcan but need not be activated by the input components 209, and conveysthe outgoing information to one or more of the wireless transceivers 201for modulation so as to provide modulated communication signals to betransmitted. The wireless transceiver(s) 201 convey the modulatedcommunication signals by way of wireless (as well as possibly wired)communication links to other devices (e.g., remote devices).

Depending upon the embodiment, the output and input components 207, 209of the components 200 can include a variety of visual, audio and/ormechanical outputs. For example, the output device(s) 207 can includeone or more visual output devices such as a cathode ray tube, liquidcrystal display, plasma display, video screen, incandescent light,fluorescent light, front or rear projection display, and light emittingdiode indicator, one or more audio output devices such as a speaker,alarm and/or buzzer, and/or one or more mechanical output devices suchas a vibrating mechanism or motion-based mechanism. Likewise, byexample, the input device(s) 209 can include one or more visual inputdevices such as an optical sensor (for example, a camera lens andphotosensor), one or more audio input devices such as a microphone, andone or more mechanical input devices such as a flip sensor, keyboard,keypad, selection button, navigation cluster, touch pad, capacitivesensor, motion sensor, and switch.

As noted, the user interface and particularly the touch screen display105 of the electronic device 100 of FIG. 1 can be considered toconstitute or include both one or more of the input components 209,particularly a touch-sensitive input component 219 shown in FIG. 2, andone or more of the output components 207. Further, it should beappreciated that the operations that can actuate one or more of theinput devices 209 can include not only the physical pressing/actuationof the touch screen display 105 or buttons or other actuators of theuser interface or otherwise, but can also include, for example, openingthe electronic device 100 (if it can take on open or closed positions),unlocking the electronic device 100, moving the electronic device toactuate a motion, moving the electronic device to actuate a locationpositioning system, and operating the electronic device.

In the present embodiment, one or more of the input components 209, suchas one or more input components encompassed by the user interface suchas the touch-sensitive component 219 shown in FIG. 1, can produce aninput signal in response to detecting a predetermined gesture. In thisregard, the touch-sensitive component 219 can be considered a gesturesensor and can be or include, for example, a touch-sensitive sensorhaving a touch-sensitive surface substantially parallel to the display.The touch-sensitive sensor can include at least one of a capacitivetouch sensor, a resistive touch sensor, an acoustic sensor, anultrasonic sensor, a proximity sensor, or an optical sensor.

As mentioned above, the components 200 also can include one or more ofvarious types of the sensors 113. Although the sensors 113 are for thepurposes of FIG. 2 shown to be distinct from the input devices 209, thesensors can also be considered as being encompassed among the inputdevices 209. In alternate embodiments, one or more of the input devicescan be encompassed among the sensors, one or more of the sensors can beconsidered distinct from the input devices, one or more of the inputdevices can be considered distinct from the sensors, or all of thesensors can be considered distinct from all of the input devices andvice-versa.

With respect to the sensors 113 particularly shown in FIG. 2, theseparticularly include various sensors 225-231 that are examples ofsensors that can be included and/or utilized by the electronic device100. As already noted, as shown in FIG. 2, the various sensors 225-231in the present embodiment can be controlled by the sensor hub 223, whichcan operate in response to or independent of the processor(s) 203. Thevarious sensors 225-231 can include, but are not limited to, one or morepower sensors 225, one or more temperature sensors 227, one or morepressure sensors 227, one or more moisture sensors 229, and one or moreambient noise sensors 231.

Further in regard to the present embodiment, and as discussed furtherbelow in regard to FIGS. 3-10B, it should further be understood that thesensor hub 223, in addition to controlling the various sensors 225-231,also serves to control operation of the touch screen display 105 of theuser interface (and the functionality that supports it) when theelectronic device 100 and particularly the touch screen display isconsidered to be “off”, including times at which the electronic deviceis operating in a “breathing mode” of operation as described below. Thisis in contrast to times at which the electronic device 100 is awake or“on”, during which times the touch screen display 105 of the userinterface (and the functionality that supports it) is under the controlof the processor(s) 203, which can be considered applicationprocessor(s). This manner of operation involving control by the sensorhub 223 at times when the electronic device is “off” is advantageousbecause the sensor hub consumes substantially less power than theprocessors 203 therefore operation under the control of the sensor hubcan be provided with substantially less battery drain than operationunder the processor(s) 203.

Although the various sensors 225-231 are shown in FIG. 2, in otherembodiments one or more of numerous other types of sensors can also beincluded among the sensors 113 including, for example, one or moremotion sensors, including for example one or more accelerometers or Gyrosensors (not shown), one or more light sensors, one or more proximitysensors (e.g., a light detecting sensor, an ultrasound transceiver or aninfrared transceiver), one or more other touch sensors, one or morealtitude sensors, one or more location circuits/components that caninclude, for example, a Global Positioning System (GPS) receiver, atriangulation receiver, an accelerometer, a tilt sensor, a gyroscope, orany other information collecting device that can identify a currentlocation or user-device interface (carry mode) of the electronic device100.

With respect to the processor(s) 203, the processor(s) can include anyone or more processing or control devices such as, for example, amicroprocessor, microcomputer, application-specific integrated circuit,etc. The processors 203 can generate commands, for example, based oninformation received from the one or more input components 209. Theprocessor(s) 203 can process the received information alone or incombination with other data, such as information stored in the memories205. Thus, the memories 205 of the components 200 can be used by theprocessors 203 to store and retrieve data.

Further, the memories (or memory portions) 205 of the components 200 canencompass one or more memory devices of any of a variety of forms (e.g.,read-only memory, random access memory, static random access memory,dynamic random access memory, etc.), and can be used by the processors203 to store and retrieve data. In some embodiments, one or more of thememories 205 can be integrated with one or more of the processors 203 ina single device (e.g., a processing device including memory orprocessor-in-memory (PIM)), albeit such a single device will stilltypically have distinct portions/sections that perform the differentprocessing and memory functions and that can be considered separatedevices. The data that is stored by the memories 205 can include, butneed not be limited to, operating systems, applications, andinformational data.

Each operating system includes executable code that controls basicfunctions of the electronic device 100, such as interaction among thevarious components included among the components 200, communication withexternal devices via the wireless transceivers 201 and/or the deviceinterface 215, and storage and retrieval of applications and data, toand from the memories 205. Each application includes executable codethat utilizes an operating system to provide more specificfunctionality, such as file system service and handling of protected andunprotected data stored in the memories 205. Such operating systemand/or application information can include software update information(which can be understood to potentially encompass update (s) to eitherapplication(s) or operating system(s) or both). As for informationaldata, this is non-executable code or information that can be referencedand/or manipulated by an operating system or application for performingfunctions of the electronic device 10.

It is to be understood that FIG. 2 is provided for illustrative purposesonly and for illustrating components of an electronic device inaccordance with the present invention, and is not intended to be acomplete schematic diagram of the various components required for anelectronic device. Therefore, an electronic device can include variousother components not shown in FIG. 2, or can include a combination oftwo or more components or a division of a particular component into twoor more separate components, and still be within the scope of thepresent invention.

Referring now to FIG. 3, represented by FIGS. 3A and 3B, a flowchart 300shows an example process performed by the electronic device 100 shown inFIGS. 1 and 2. The flowchart 300 particularly illustrates example stepsof operation of the electronic device 100 as the electronic deviceproceeds among different operational modes or states, mainly, a “fullyawake” or “on” mode of operation during which the processors 203 areoperating (that is, the application processors are up and running), an“off” mode of operation, and an “intermediate” mode of operation duringwhich breathing and peeking processes (as discussed in further detailbelow) occur or can occur. Although in the present embodiment theprocessors 203 are off or powered-down during the off mode andintermediate mode of operation (by contrast to operation in the fullyawake mode, during which the processors 203 are up and running), as willbe described further below it is still possible for the electronicdevice 100 to operate during one or both of the off mode andintermediate mode in manners that involve some display functionality bythe touch screen display 105 (including potentially both outputting ofinformation and receiving of inputs). Such operation of the touch screendisplay 105 during the intermediate mode and/or off mode is achieved byvirtue of control functionality provided by the sensor hub 223.

More particularly, in FIG. 3, portions of the process represented by theflow chart 300 that occur in the fully awake mode are shown within afully awake mode region 302, and portions of the process thatcorresponds to the off mode are shown in a region 304. This being thecase, it should further be appreciated that all of the remainingportions of the process shown in FIG. 3, excluding the portions shown inthe regions 302 and 304, are portions of the process that are performedduring the intermediate mode of operation, and are referred to as beingwithin a region 306 shown in FIG. 3. It should further be appreciatedthat, generally speaking, operation in the fully awake mode isassociated with a normal power mode of the processors 203 (applicationprocessors) and/or a substantially active mode of those processors. Bycontrast, the intermediate mode of operation and off mode of operationare associated with a low power (or even completed powered-off) mode ofthe processors 203 (application processors) and/or a substantiallyinactive mode of those processors. Given the above, the intermediatemode of operation can also be referred to as an “Always on Display” mode(AoD) mode or “sleep” mode (and/or the off mode potentially can also beencompassed generally within the “sleep” mode), in contrast to the fullyawake mode, which can be referred also to a “non-sleep” mode.

Additionally as will be described further below, in at least someembodiments disclosed herein, one or more notifications can be displayedby the electronic device 100 in a “non-sleep” mode such as the fullyawake mode and also one or more notifications can be displayed by theelectronic device in a “sleep” mode such as the intermediate or AoD mode(including submode portions thereof as described). In at least some suchembodiments, the notifications provided in the fully awake mode or“non-sleep” mode are notifications received during operation in thatmode, and that are displayed by way of activation of the entire, orsubstantially the entire, display screen (e.g., full screen informationis displayed, where the full screen information includes datacorresponding to substantially all pixels capable of being displayed bythe display). Further in such embodiments, in contrast, thenotifications provided in the intermediate mode or “sleep” mode arenotifications received during operation in that mode, and that aredisplayed by way of activation of only a portion or portions of thedisplay screen (particularly portion(s) that are substantially less thanthe entire display screen and/or display substantially less that thefull screen information, that is, information corresponding to less orsubstantially less than all pixels capable of being displayed by thedisplay).

Further referring to FIG. 3, as indicated by first and second startregions 308, the process represented by the flow chart 300 can begineither in the fully awake mode or the off mode. Operation in the fullyawake (or on) mode begins particularly with a step 310, at which thetouch screen display (or other display screen) 105 is on. It should beunderstood that, during such fully awake mode operation, the electronicdevice 100 can (and typically does) receive one or more notifications.Such notifications can take any of a variety of forms including, forexample. email messages, short message service (SMS) text messages,various updates or alerts, or other forms, and such notifications can bereceived at the electronic device 100 in any of a variety of mannersincluding, for example, by way of wireless signals received via thewireless transceivers 201 from other electronic devices such as remotedevices (not shown). In response to receiving such notifications, orsignals or other information giving rise to notifications, in the fullyawake mode, the electronic device 100 typically will displaynotifications on the touch screen display 105 corresponding to thereceived notifications, signals, or information. Such display, under thecontrol of the processors 203, typically involves actuation of theentire touch screen display.

Nevertheless, at some point during the operation of the electronicdevice 100 in fully awake mode, as represented by a step 312, the touchscreen display can turn off as a result of a timeout (a the passing of apredetermined amount of time during which no activity or activities ofpredetermined type(s) have occurred), as a result of a toggle buttonpressed by the user, or as a result of other condition(s) being met.When this occurs, the process then advances to a step 314, at which theoff mode is entered and the touch screen display 105 remains off (to beclear, at this step in the off mode, no breathing or other intermediatemode functionality is performed). It should further be noted that theprocess represented by the flow chart 300 can also begin, as indicatedby one of the start regions 308, at this step 314 as well, whichreflects the possibility that the process starts at a time when theelectronic device 100 is already in the mode.

Further as shown, if a power button press occurs at a step 316 while thescreen is in the off mode, then the electronic device 100 can return tothe fully awake mode, by proceeding from the step 316 to a step 318, atwhich the electronic device is awakened, after which the process againreturns to the step 310 at which the touch screen display 105 is on.Alternatively, however, if while the electronic device is in the offmode and the touch screen display 105 is off at the step 314 and a newnotification arrives as represented by a step 320, then the electronicdevice 100 also re-enters the fully awake mode. As already discussedabove in regards to the step 310, depending upon the embodiment orcircumstance the received notification can take any of a variety offorms. Further, upon receipt of a new notification at the step 320, thenat a step 322 filtering is applied by the electronic device 100 todetermine whether or not the received notification satisfies one or morecriteria such that the notification is appropriate for being displayedin any particular manner.

The filtering that is performed at the step 322 can vary depending uponthe embodiment or circumstance. For example, in some embodiments,certain types of notifications are “blacklisted”, that is, automaticallydetermined to be not worthy of triggering operation of the electronicdevice 100 that would result in immediate display of those items. Insome such embodiments, some or all of the rules defining what types ofnotifications are “blacklisted” can be static, but in other embodiments,some or all of the rules are user-modifiable (e.g., the user can selectand modified by a user of the electronic device through a settingsfeature of the electronic device). Also, in some such exampleembodiments, the rules are global in terms of the rules impactingwhether the notification is synced to all end points (e.g., a phone, awatch, a personal computer operating a browser such as Chrome browseravailable from Google, Inc. of Mountain View, Calif.), but in other suchexample embodiments the rules are not global. Further for example, insome embodiments certain types of notifications are “whitelisted”, thatis, automatically determined to be worthy of triggering operation of theelectronic device 100 that would result in immediate display of thoseitems.

Further, in regards to such filtering, it should also be appreciate thatthe filtering that is performed vary depending upon whether theelectronic device 100 is operating in the fully awake mode, in theintermediate mode, or in the off mode. Indeed, more generally, thefiltering that is performed can vary generally with respect to the modeof operation of the electronic device, and it should be understood thatthe present disclosure envisions the possibility of embodiments (andencompasses embodiments) in which there are more modes of operation ofthe electronic device other than the fully awake mode, intermediatemode, and off mode, and also envisions that the modes of the electronicdevice can include “sub-modes” corresponding to operations thatconstitute sub portions of the functionality associated with any givenmode of operation—for example, modes such as a breathing mode ofoperation and a peek view mode of operation can be considered to besub-modes encompassed by the intermediate mode as discussed in furtherdetail below. Notwithstanding the particular terminology used here in torefer to various modes (and sub-modes), it should be appreciated thatother terminology can also be chosen to refer to these modes (andsub-modes) as well. For example, it is possible that the term “breathingmode” can be used to refer to all functionality described herein asbeing associated with the “intermediate mode”, including “peek viewmode” operation, and that the particular functionality associated withthe “breathing mode” as described herein can be referred to in adifferent manner. (Nevertheless, for purposes of the descriptionprovided herein, the “intermediate mode” encompasses the “breathingmode” and “peek view mode” operation).

Additionally, it should be appreciated that filtering can encompassnumerous different types of filtering steps and processes depending uponthe embodiment or circumstance including, for example, a variety ofdifferent type of rule application steps, ranking steps, and/or stepsinvolved with processing or mining data (e.g., analyzing orcross-referencing strings of text or detecting names in various textstrings) packages, or applications.

Subsequent to (or as a conclusion of) the step 322, as furtherrepresented by a step 324, the electronic device 100 determines whether,based upon the filtering, the received notification does meet one ormore criteria for display in the intermediate mode (or AoD mode as notedabove). If so, as shown in FIG. 3 the process leaves the fully awakemode and enters the intermediate mode as indicated by an arrow 325crossing out of the fully awake mode region 302 and entering theintermediate mode region 306. More particularly, upon entering theintermediate mode region 306, the process particularly reaches a step326 at which breathing operation is begun (or, if already beingperformed, continues to be performed). Example breathing operation,which can be referred to as operation in the breathing mode (which asnoted above can be considered a sub-mode of the intermediate or AoDmode), is described in further detail below with respect to FIGS. 4Athrough 10B.

Alternatively, if at the step 324 it is determined that the receivednotification does not (based upon the filtering of the step 322) meetthe criteria for display in the intermediate mode, then the processadvances from the step 324 to a step 328. At the step 328, it isdetermined by the electronic device 100 whether breathing operation (inaccordance with the breathing mode) was already in progress and beingperformed. If breathing operation was already in progress, then theprocess advances from the step 328 back to the step 326, and thebreathing operation already going on continues on with no change, thatis, the electronic device continues unabatedly to perform breathingoperation like normal. However, if at the step 328 it is determined thatthe breathing operation was not already in progress, then the processreturns from the step 328 back to the step 314 such that the processreturns to the off mode and particularly the touch screen display 105 isoff and no breathing is occurring (accordingly, there is no change tothe breathing operation and the screen remains off).

As additionally shown in FIG. 3, and discussed in further detail belowwith respect to FIGS. 4A through 10B, when the electronic device 100 hasreached the step 326 of the intermediate mode so as to be operating inthe breathing mode, breathing operation can then continue onindefinitely. Nevertheless, there are several actions or events canoccur that cause the breathing operation to be stopped and/or to causethe mode of operation to change. First, as shown in FIG. 3 by a step330, if a power button press is received at the electronic device 100,then the electronic device returns to the fully awake mode andparticularly the process advances to a step 332 within the fully awakemode region 302 in which the electronic device is awakened (andparticularly the processors 203 are powered on) and accordingly thebreathing operation of the step 326 is ended. Such a power button pressoperation can also be considered a “home button” press, if one views thefully awake mode as a “home” mode. Following the step 332, the processthen additionally returns to the step 310, at which the touch screendisplay 105 is on (and received notifications are displayed thereon).

Alternatively, as represented by an arrow 333 linking the step 326 tothe step 320, it is also possible during the breathing operation of thestep 326 that a further new notification is received by the electronicdevice 100, as represented again by the step 320. If this occurs, thenthe process again advances through the steps 320, 322, 324, and possiblythe step 328, after which the process returns to the step 326. That is,when a new notification is received, ultimately the breathing operationof the step 326 continues, either because the received notificationmeets the criteria for being displayed in the intermediate mode asdetermined at the step 324, or because breathing operation has alreadybeen in progress as determined at the step 328. It should be appreciatedthat, although the steps 320, 322, 324, and 328 are shown to beencompassed within the fully awake mode region 302, it is possible inalternate embodiments that these steps of receiving a new notificationwhen the electronic device 100 is in the breathing mode and filteringand responding to the new notification can all be performed as part ofthe intermediate mode of operation, in at least some alternateembodiments.

Additionally as shown in FIG. 3, in some circumstances, during thebreathing operation of the step 326, a user can touch a “hit area” onthe touch screen display 105, particularly at a time when the touch isactive during a breath, as described in more detail below with respectto FIG. 9, represented by FIGS. 9A and 9B. If such a touch occurs at astep 334, then the process advances to a step 336, in which theelectronic device 100 remains in the intermediate mode (AoD mode) ofoperation but in which a peek view can occur. Such peek view operationrepresented by the step 336 can be considered to constitute a peek viewmode of operation that is a submode of the intermediate mode (thetransition step 334 at which the user touches the hit area can beconsidered to be part of either the breathing mode or the peek viewmode). Execution of operations as part of the peek view mode asrepresented by the step 336 can ultimately, as discussed in relation toFIG. 9, result in the process returning to any of a variety of modes, asrepresented by an arrow 337 of FIG. 3, including the breathing mode(corresponding to the step 326), the fully awake mode, or the off mode.

Finally, also as shown in FIG. 3, it is also possible that duringoperation in the breathing mode corresponding to the step 326 that anincoming call, alarm, or other wakeup event not initiated by a power key(or button) press or touch screen interaction or encompassed within thenotifications addressed by the step 320 (in other words, some other typeof notification that does not correspond to any of the steps 320, 330,or 334) will occur. If such an event occurs, then the process of theflow chart 300 advances to a step 339 at which the electronic device 100is awakened and the fully awake mode region 302 is reached again.However, subsequent to the step 339, if there occurs a time at which thetouch screen display 105 turns off as represented by a step 340, thenthe process returns back to the intermediate mode and particularly tothe step 326 and breathing again resumes.

Referring now to FIGS. 4A, 4B, 4C, and 4D, respectively, first, second,third, and fourth example views of the touch screen display 105 of theelectronic device 100 are shown that are intended to illustrate exampleoperation of the touch screen display in displaying images duringvarious portions of the process represented by the flow chart 300 ofFIG. 3, particularly during the breathing and peek view modesencompassed the intermediate mode (the portions of the processcorresponding to the intermediate mode region 306). FIG. 4A particularlyshows a blank image 400 that appears when the touch screen display 105is completely off. As discussed further below in regard to FIG. 6, theblank image 400 appears at particular times during breathing operationcorresponding to the step 326.

By contrast, FIG. 4B shows a breathing view image 402 that, rather thanbeing blank, instead includes one or more image portions that aredisplayed by the touch screen display 105, and which the present exampleparticularly include an icon 404 that can constitute a hit area that canbe touched by a user during operation in the breathing mode (e.g., atthe step 334 of FIG. 3), additional icons 406 that also can constitutean additional hit area (or areas), and a time display 408. As discussedfurther with respect FIG. 6 (and FIG. 7), the breathing view image 402does not remain consistently on at all times during operation in thebreathing mode, but rather periodically becomes visible and thendisappears (at which times the touch screen display 105 again takes onthe blank image 400 of FIG. 4A.

Next, with respect to FIG. 4C, a peek animation image 410 isillustrated. As shown, the peek animation image 404 also includes one ormore image portions that are displayed by the touch screen display 105,and more particularly in this embodiment these one or more imageportions include not only all of the image portions shown in FIG. 4B(namely, icon 404, icons 406 and time display 408) but also additionallyinclude animation features 412, which in the present example includeupper and lower (that is, above the time display 408 and below the icons406) vertically-extending columns of three dots. As further discussedbelow, the animation features 412 particularly are displayed by thetouch screen display 105 during transitioning between a time during thebreathing mode at which a touch can be received (e.g., a time at whichthe breathing view image 402 shown in FIG. 4B is displayed), and a timeat which the peek view mode has been fully entered and a peek view imagesuch as an example image shown in FIG. 4D is displayed. As with the step334 of FIG. 3, the displaying of the peek animation view of FIG. 4C canbe considered either as part of the breathing mode or as part of thepeek view mode.

Additionally, with respect FIG. 4D, the peek view image 414 showntherein is an example of an image that can be displayed by the touchscreen display 105 once peek view mode has been entered. As shown, thepeek view image 414 no longer includes the exact same arrangement ofimage portions shown in the peak animation view 410, albeit some of theimage portions are the same in terms of their respective appearances.More particularly, the peek view image 414 in contrast to the peakanimation image 410 no longer has the animation features 412 or timedisplay 408, but continues to have an icon 405 identical in appearanceto the icon 404 and icons 407 identical in appearance to the icons 406,except insofar as the icon 405 is now at a location that is movedupwards relative to the location of the icon 404 in the peek animationview (above the location of the uppermost dot of the upper column ofdots of the animation features) and the icons 407 are now at a locationthat is moved vertically downward relative to their previous location inthe peek animation view (below the location of the lowermost dot of thelower column of dots of the animation features).

Further, in the peek view image 414, one or more (in this example,three) text strings lines 416 are also displayed, above the icon 405.The text string lines 416 can include message information or informationcorresponding to one or more past notifications received by theelectronic device 100. The display of these text string lines thusallows the user to “peek” at the notifications that have been received(e.g., recently received) by the electronic device 100, and is thereforethe feature of this manner of operation giving rise to the “peek viewmode” terminology used herein.

Referring additionally to FIGS. 5A, 5B, 5C, and 5D, first, second,third, and fourth additional views 500, 502, 510, and 514, respectively.The first, second, third, and fourth views 500, 502, 510, and 514respectively encompass the respective blank, breathing view, peekanimation view, and peek view images 400, 402, 410, and 414 that areshown in FIGS. 4A, 4B, 4C, and 4D, respectively, but also show thoseimages in combination with illustrations of a user—particularly a finger512 of the user's hand—interacting with those images. Because it isenvisioned that the finger 512 of the user has not yet approached thetouch screen display in the case of the blank image 400 and breathingview image 402, the first additional view 500 of FIG. 5A merely againshows the blank image 400, and the second additional view 502 of FIG. 5Bmerely again shows the breathing view image 402. By contrast, withrespect to the third additional view 510 of FIG. 5C, there it isenvisioned that the user has already touched the touch screen display105 with the user's finger 512 and this has given rise to display of thepeek animation view 410. In particular, it should be noted that thefinger 512 is touching on the icon 404, which constitutes one of the hitareas on the touch screen display 105 in this example. Further, it isbecause of (in response to) the user's finger 512 touching the hit areathat animation features 412 are shown to have appeared (as discussed inmore detail below in regard to FIG. 9, the animation featuresprogressively appear as a response to the touching of one of the hitareas).

Finally, at FIG. 5D, the fourth additional view 514 shows the peek viewimage 414 of FIG. 4D and also again shows the user's finger 512 to stillbe proximate to (touching) the touch screen display 105. As representedby arrows 515, while in the peek view mode of operation, the user canfurther provide a gesture (or gesture portion) so as to actuate theelectronic device 100 to perform one of several different actions ortransition to any of several different modes (again as discussed furtherbelow in reference to FIG. 9). In the present example, gesturalactuation of the electronic device 100 in this regard particularly isnot accomplished until, in addition to originally touching one of thehit areas (again, in this example, one of the icons 404 and 406) duringthe breathing mode of operation, the user then further: (i) continues tocontinuously touch that hit area during the transitioning from thebreathing mode to the peek view mode (e.g., continues to touch one ofthe icons 404, 406 as the touch screen display transitions from thebreathing view 402 to the peak animation view 410 and ultimately to thepeek view 414); (ii) then manipulates the finger 512 to slide upward ordownward (e.g., in accordance with either of the arrows 515 of FIG. 5D)until the finger reaches an appropriate one of the image portions of thepeek view image corresponding to the hit area that was originallytouched (e.g., reaches one of the icons 405, 407 as shown in the peekview 414), and (iii) then releases the hit area by removing the finger512 from the touch screen display.

Turning now to FIG. 6, a modified flow chart 600 is provided toillustrate example operation of the electronic device 100, and moreparticularly operation of the touch screen display 105 of the electronicdevice, during operation in the breathing mode corresponding to the step326 of the process of the flow chart 300 of FIG. 3. The modified flowchart 600 includes first, second, third, and fourth steps 602, 604, 606,and 608, respectively, of the operation in the breathing mode. The firststep 602 particularly represents a stage of breathing operation in whicha breathing view image is displayed on the touch screen display 105 atmaximum brightness. As an example, FIG. 6 shows the breathing view image402 of FIG. 4B to be the breathing view image that is displayed (whichagain includes the icon 404, icons 406, and time display 408). However,it should be appreciated that the breathing view image 402 is merely oneexample of many images and image portions that can be displayed as thebreathing view image. Display of the breathing view image at the maximumbrightness can also be referred to as providing the breathing view imageat a breathing plateau, as will be described further in relation to FIG.7.

Of further significance in regard to the step 602 is that it can be seenthat all of the relevant displayed image portions (again, the icon 404,icons 406, and time display 408) are located within a first partialregion 610. With respect to the first partial region 610, it should beunderstood that this is not a physical feature but rather is merelydefines a region encompassing a portion of the space occupied by thetouch screen display as well as possibly a portion of space outside ofthe confines of that display. Thus, although the partial region 610 inthe present example is shown as extending beyond the confines of thebreathing view image 402, which corresponds to the physicalboundary/border of the touch screen display 105, the partial region 610in fact is intended to refer to that portion of the touch screen display105 that is within that boundary, rather than the entire space definedby that boundary.

Further, it should be understood that the first partial region 610 doesnot constitute an actual displayed image item on the touch screendisplay 105 (such as a rectangular portion of the touch screen displaythat might be illuminated as such), but rather merely indicates aportion of the touch screen display that is capable of being actuated.Thus, in the present example, the touch screen display 105 is only beingactuated to display image portions that happen to be positioned atlocations (at pixel locations) on the display that are within thepartial region 610, but is not being actuated to display any imageportions that happen to be positioned at locations (at pixel locations)on the display that are within either of an upper region 612 above, or alower region 614 below, the partial region 610 on the touch screendisplay 105. That said, to the extent that the image portions positionedwithin the partial region 610 (in this case, again, the icon 404, icons406, and time display 408) are positioned within that partial region610, the partial region 610 itself can be said to include those imageportions. That is, for convenience of referencing the image portionsthat are within the partial region 610, one can refer to displaying ofthe partial region 610 itself as a manner of referring to the displayingof the image portions that happen to be physically located within thespace corresponding to that partial region (again, in this case, theicons 404 and 406 and time display 408).

Still referring to FIG. 6, in the present embodiment, the partial region610 (that is, the image portions positioned therewithin) is displayed atthe first step 602 with maximum brightness (at a plateau). After aperiod during which the partial region 610 is displayed with the maximumbrightness, the touch screen display 105 is actuated so that thebrightness of the partial region 610 is decreased, until as illustratedin the second step 604 the displayed brightness level is reduced to aminimum. As will be discussed further in regard to FIG. 7, thetransition between the maximum brightness level associated with theplateau and the minimum brightness level can occur over a specificamount of time. This operation in which the brightness level is reducedcan be considered to be represented by an arrow 616 linking the firststep 602 and the second step 604.

When the minimum brightness level is reached as represented by thesecond step 604, the partial region 610 (again, that is, the imageportions contained therewithin) is still being displayed, because thetouch screen display is still on (in accordance with intermediate modeoperation as controlled by the sensor hub 223). However, the partialregion 610 (that is, the image portions contained therewithin) are nolonger visible to the user once the process reaches the second step 604because the brightness level at which the partial region is beingdisplayed is the minimum level. Even so, at this point, the touchsensing capability of the touch screen display 105 and particularly thetouch sensing capability of the touch screen with respect to the hitareas (e.g., the icons 404 and 406) remains active. That is, generallyspeaking, the touch sensing capability of the touch screen display 105during breathing operation remains active at all of the times duringwhich the brightness level of the partial region 610 on the touch screendisplay is at a maximum, a minimum, or anywhere in between (e.g., duringthe time of transition between the first and second steps 602 and 604 asrepresented by the 616).

In contrast to the second step 604, at the third step 606 the touchscreen display 105 is completely off and the image displayed at thatpoint not only is entirely blank (e.g., such as the blank image 400 ofFIG. 4A), but also the touch screen sensing capability of the touchscreen display 105 is completely off. The transition from the secondstep 604 to the third step 606 is represented by an arrow 608, whichindicates that, after reaching the completely blank but stilltechnically-on status represented by the second step 604, the touchscreen display and touch capability thereof are completely turned off.The amount of time in which the touch screen display 105 remainscompletely off at the third step 606 can vary depending upon theembodiment or circumstances. Throughout this time period, the electronicdevice 100 continues to be operating in the breathing mode, even thoughthe touch screen display 105 is blank and non-responsive to usertouches.

Ultimately, the off time corresponding to the third step 606 iscompleted and the touch screen display 105 and the touch capabilitythereof are turned back on, as a result of a transition represented byan arrow 620 leading to the fourth step 608. That is, upon completion ofthis transition, the process reaches the fourth step 608, at which thebreathing view image and particularly the first partial region 610 (thatis, the image portions contained therewithin) is again displayed withminimum brightness in the same manner as was the case at the second step604. Thus, again in this example the touch screen display 105 at thisstep is blank, but that the touch capability of the touch screen display105 within the partial region 610 is active. Following the fourth step608, the process returns to the first step 602, at which breathing viewimage 402 and particularly the partial region 610 (that is, the imageportions contained therewithin) are displayed with maximum intensity.The transition from the fourth step 608 at which the touch screendisplay 105 is at the minimum brightness level to the first step 602 atwhich the touch screen display is at the maximum brightness level isrepresented by an arrow 622 linking those steps. Upon reaching the step602, the touch screen display 105 remains at the maximum brightnesslevel, at the breathing plateau, for an additional amount of time thatcan be the same as when the step 602 was earlier performed or for adifferent amount of time, depending upon the embodiment or operationalcircumstance.

It should also be appreciated that the exact manner in which thetransitioning occurs among the different brightness levels correspondingto the steps 602, 604, 606, and 608 of operation in the breathing modeas shown in FIG. 6 can vary depending upon the embodiment orcircumstance. Referring to FIG. 7 in particular, a timing graph 700shows one example of how the on/off status and the brightness levels ofthe touch screen display 105, in terms of displaying image portions andparticularly partial regions(s) in relation to which the touch screendisplay is configured to receive touches (e.g., the partial region 610),can vary with time. FIG. 7 particularly shows how the brightness levelsof the touch screen display 105 vary with time between a minimumbrightness level 702 and a maximum brightness level 704. Moreparticularly as shown, in this example, the increase in brightnessbetween the minimum brightness level 702 and the maximum brightnesslevel 704 that occurs between the steps 608 and 602 of FIG. 6 (asrepresented by the arrow 622) is shown in FIG. 7 to occur, between atime 706 and a time 708, in a linear manner shown as a linear portion709. However, in alternate embodiments, the ramping up can be inaccordance with any linear, logarithmic, sinusoidal, or other type ofmanner.

Further as shown in FIG. 7, upon reaching the maximum brightness levelat the time 708, the touch screen display 105 operates to display abreathing view image (for example, the breathing view image 402 of FIG.4B including the first partial region 610) at the maximum brightnesslevel until a later time, which in this example is a time 710. Thisperiod of time during which the touch screen display 105 is at itsbrightest level can be referred to as the “breathing plateau”. In thisregard, it should be appreciated that the amount of time at which themaximum brightness level is exhibited, that is, the difference in thetimes 710 and 708, can vary depending upon the embodiment, as well asthe operational circumstance. For example, in some embodiments, the timeof the plateau can be longer for breaths that are triggered by newnotifications and/or device gestures than for other breaths. That is,further for example, the continually-repeating breaths performed at thestep 326 can generally have plateaus of a consistent length but, in theevent the process 300 involves a new notification in accordance with thearrow 333 and step 320 of FIG. 3, or some other type of event for whichan elongated plateau is appropriate (e.g., as discussed in regard toFIGS. 9 and 10A-10B below), then the next breath performed at the step326 can have a plateau of a longer time length.

Subsequent to the time 710, the brightness level of the touch screendisplay 105 is reduced back down again up until a time 712, at which theminimum brightness level is reached, an operation corresponding to thetransition represented by the arrow 616 of FIG. 6 between the first(maximum brightness) step 602 and second (minimum brightness) step 604.This reduction in brightness is again shown in FIG. 7 to occur in alinear manner as represented by a linear portion 711. That said, thereduction in other embodiments can occur by way of a linear,logarithmic, sinusoidal, or other type of manner. Subsequently, afterthe minimum brightness level is reached at the time 712 corresponding tothe step 604, instantaneously or almost instantaneously the touch screendisplay 105 then turns off in accordance with the step 606 (that is, theperforming of the transition from the second step 604 to the third step606 as represented by the arrow 618 of FIG. 6 can occur instantaneouslyor substantially instantaneously). Then, from the time 712 to a time714, the touch screen display 105 is off and not displaying anything.

It should be appreciated that the display operations between the times706 and 712, in which the breathing view image (e.g., the image 402 ofFIG. 6) becomes brighter, then plateaus, and then becomes dimmer, can beconsidered a “breath” during breathing operation of the electronicdevice. Additionally, it should also be appreciated that the exactamount of time that the touch screen display 105 is off following such abreath can vary depending upon the embodiment or circumstance, and canvary during operation of the electronic device 100 over time. Forexample, in some embodiments, the off time will increase so as to “slowdown” the breathing operation when it is detected that there is verylittle (or has been very little) activity of the electronic device.

Finally, in correspondence with the transition from the third (screenoff) step 606 to the fourth (minimum brightness) step 608 of FIG. 6 asrepresented by the arrow 620, FIG. 7 includes an arrow 716 by which itis indicated that the off status of the touch screen display 105 isultimately concluded and the process transitions again to a period ofincreasing brightness beginning again at the time 706 at which the touchscreen display is on and at its minimum brightness level. It should beappreciated that, although the arrow 716 of the timing graph 700 of FIG.7 shows the process as returning to the time 706, this should beunderstood merely as an indication that the breathing loop continuesrepetitively, and not that the operation returns to the exact samemoment in time at which the operation first begin. That is, when theprocess repeats itself, it begins again at a time later than the time714, or possibly at the time 714 itself, which would correspond to anunderstanding that the arrow 716 represents an instantaneous transition.

In view of FIGS. 6 and 7, it should be appreciated that the breathingmode of operation corresponding to the step 326 of the process 300 ofFIG. 3 can involve a continual repetition of (cycling through of) thesteps 602, 604, 606, and 608 (and transition steps in betweenrepresented by the arrows 616, 618, 620, and 622) over an indeterminatelength of time. From the above, it will be appreciated that a number ofparticulars regarding these steps of the breathing mode, as well as anoverall duty cycle for this mode, can vary depending upon theoperational circumstance (e.g., the time length of the plateau or offperiod), and further that such particulars can also be varied dependingupon the operational circumstance (e.g., a duty cycle of the breathingoperation can be reduced when the electronic device is not being used).Nevertheless, as will be appreciated, the overall nature and ordering ofthese breathing steps remains the same as the breathing operationproceeds.

Thus, during operation in the breathing mode, a user experiences theelectronic device as a device that substantially or largely appears tobe “off” insofar as much of the time the touch screen display is blank,but that occasionally displays, in gradually-appearing andgradually-disappearing manner, image portions indicating that there maybe items/notifications of interest for the user. That said, althoughthis breathing mode of operation can continue on indefinitely, asalready discussed in regard to FIG. 3 and as discussed further below,the electronic device 100 nevertheless can exit the breathing mode toanother mode of operation, such as the peek view mode of operation orout of the intermediate mode to either the fully active mode or offmode, under any of a number of circumstances.

Turning now to FIGS. 8A and 8B, as already discussed to some extent inrelation to FIGS. 4A-4D, 5A-5D, and 6, in the present embodiment duringoperation in the intermediate mode corresponding to the region 306 ofFIG. 3, specific portions of the touch screen display 105 of theelectronic device 100 (to the exclusion of other portions of the touchscreen display) are actuated at particular times so as to displayparticular image portions and/or so as to be able to receive particulartouch inputs. The specific portions of the touch screen display 105 thatare actuated in this regard can depend upon the embodiment oroperational circumstance. Nevertheless, in the present embodiment, allof the image portions corresponding to each of the different images arestored in a single frame buffer that determines all of the imageportions available for display during operation in the intermediatemode.

For example, in regard to the image portions of FIGS. 4A-4D, as alreadydiscussed, display of the peak animation view 410 involves the displayof different image portions (e.g., the icons 404 and 406, and timedisplay 408) than those which are displayed in the peek view 414 (e.g.,the animation portions 412, icons 405 and 407, and text string lines416). Nevertheless, these different image portions are located indifferent regions of the touch screen display 105, and consequently allof these image portions can be stored as a full image in a single framebuffer 800 corresponding to an overall display screen view as shown inFIG. 8A. In this regard, the frame buffer 800 can further be consideredto be a set of image portions/image information that is stored in thememory devices 205 of the electronic device 100 and that is utilized bythe sensor hub 223 as it controls operation of the touch screen displayduring operation in the intermediate mode, including the breathing modeand the peek view mode respectively corresponding to the steps 326 and336 of FIG. 3. It should be noted that the information stored in thisregard can vary over time, for example, as new notifications arise(e.g., in which case one or more the text string lines 416 couldchange).

Referring further to FIG. 8B, given a frame buffer such as the framebuffer 800 shown in FIG. 8A, it should be appreciated that the touchscreen display 105 can be controlled so as to display, and/or so as tobe capable receiving touch inputs, specifically in relation toparticular ones of the image portions in the frame buffer if the touchscreen display is divided into different partial regions thereof thatcan be actuated independently. Actuation of partial regions of the touchscreen display 105 (which can particularly entail, for example,actuation of certain ranges of rows of pixels or ranges of columns ofpixels on the display), rather than the entire display, can beadvantageous from the standpoint of saving power as well and reducingthe chance that the display is actuated to too great an extent thatdamage could result.

In the example provided by FIG. 8B, a diagram 802 particularly shows howthe touch screen display 105 can be divided into five partial imageregions that respectively overlay and encompass specific image portionsfrom the full image corresponding to the frame buffer (as illustrated bythe frame buffer 800). As shown, FIG. 8B not only includes the firstpartial region 610 already discussed in relation to FIG. 6, butadditionally includes a second partial region 804, a third partialregion 806, partial region 808, and a fifth partial region 810, where inthis example each of the successive partial regions 610, 804, 806, and808 encompasses and extends beyond the preceding partial region, exceptfor the fifth partial region 810, which encompasses different parts ofthe touch screen display other than those encompassed by the partialregions 610, 804, 806, and 808.

More particularly, as already discussed with respect to the firstpartial region 610 in relation to FIG. 6, that region encompasses andcan be said to include the image portions of the breathing view 402 ofFIG. 4B that is, the icons 404 and 406 and the time display 408. Bycontrast, the second partial region 804 encompasses everythingencompassed within the first partial region 610 and additionallyincludes first portions of the animation features 412 shown in FIG. 4C,which in this example include a first (innermost) one of each of thecolumns of the dots above the time display 408 and below the icons 406,respectively. Further as shown, the third partial region 806 encompassesall of the image portions encompassed within the second partial region804, and further encompasses the second (or middle) one of each of thecolumns of the dots encompassed within the animation features 412.Additionally as shown, the fourth partial region 808 encompasses all ofthe image portions encompassed with the third partial region 806, andfurther encompasses the third (or outermost) one of each of the columnsof the dots encompassed within the animation features 412. Thus, thepeek animation view 410 in FIG. 4C is a view in which the touch screendisplay is being actuated to display and potentially receive touchinputs at the fourth partial region 808.

As for the fifth partial region 810 of FIG. 8B, as already noted thispartial region (unlike the partial regions 610, 804, 806 and 808) doesnot encompass any of the other partial regions but rather encompassessubstantially all of the remaining sections of the touchscreen display105 that are excluded from the fourth partial region 808. The fifthpartial region 810 as shown particularly includes both a region abovethe fourth partial region 808 as well as a portion below the fourthpartial region 808. The fifth partial region 810 particularly thereforeis suited for encompassing the image portions corresponding to the peekview image 414 shown in FIG. 4D (and FIG. 5D), particularly, the icon405 and the text string lines 416 in their position near the upper endof the touch screen display 105 as well as the icons 407 in theirposition proximate the bottom of the touch screen display.

Turning next to FIG. 9, represented by FIGS. 9A and 9B, an additionalmodified flow chart 900 is provided that illustrates, partly by way of aseries of additional example views of the touch screen display 105 ofthe electronic device 100, example operation of the electronic device100 as it transitions between the breathing and the peek view modes ofoperation, which together form the intermediate mode of operationencompassed by the intermediate region 306 of FIG. 3, as well as furthertransitioning between that intermediate mode and the non-breathing mode(off mode) corresponding to the region 304 of FIG. 3. The processrepresented by the flow chart 900 is shown to begin in either of twomanners as indicated by first and second start indicators 902 and 940,respectively.

Upon beginning at the first start indicator 902, the process commencesoperation in the breathing mode at a step 904 corresponding to the step326 of FIG. 3 as well as to the discussion above pertaining to FIG. 6.As indicated in FIG. 9, the electronic device 100 is operating in thebreathing mode particularly because (in accordance with the steps 320,322, and 324 of FIG. 3) there have already been received one or morenotifications and it has been determined that those notifications areappropriate to justify displaying breaths in accordance with operationin the breathing mode as described in relation to FIGS. 6 and 7.Accordingly, as an example, the step 904 includes a diagram 903 with thebreathing view image 402 of FIG. 4B. Additionally, the diagram 903 showsthe first partial region 610 since, in the present example, the touchscreen display 105 is operated to display only the first partial region610 (that is, image portions contained therewithin) and none of thepartial regions 804, 806, 808, or 810 of FIG. 8B. It should be furtherappreciated that, although the flow chart 900 of FIG. 9 concerns thetransitioning from the breathing mode to the peek view mode, if notransition was to occur, then the breathing process would continue asdiscussed already in relation to FIG. 6 (until such time as anothertransition out of the breathing mode was appropriate in accordance withFIG. 3).

In addition to showing the breathing view image 402 (and partial region610), the diagram 903 illustrating the step 904 of FIG. 9 further showsthe user's finger 512 positioned in relation to a hit area included withthat image (in this case, the icon 404), so as to illustrate acircumstance where the user is providing a touch input in response thedisplaying of a breath. It is such a touch input, provided at a hit areaduring a breath, in accordance with the step 334 of FIG. 3, that cantrigger a transition from the breathing mode to the peek view mode. Thatis, in accordance with the breathing mode of operation, the touchscreendisplay 105 is not ready to receive user touches in relation to a hitarea such as the icon 404 at times (such as at the step 606 in FIG. 6)when the breathing view image 402 is not being displayed, but rather isonly receptive to touches when the breathing view image is present(e.g., between the times 706 and 712 illustrated in FIG. 7). At the step904, it is presumed that the breathing view image 402 is being displayedand that the touch screen display 105 is being operated to be receptiveto a touch by a user finger 512.

Upon the user touching the hit area at a time when the touchingcapability is active, the process of the flow chart 900 then advancesfrom the step 904 to a step 906 as indicated by an arrow 905, and thestep 906 is then subsequently followed in rapid succession by a step908, a step 910 and a step 912. The steps 906, 908, and 910 particularlyillustrate that, so long as the user continues to touch the hit area(e.g., the icon 404) continuously with the user's finger 512 as shown,then the touch screen display 105 transitions from displaying only theimage portions contained in the first partial region 610 to the only theimage portions contained in the second partial region 804 (such thatinnermost dots of the columns encompassed by the animation features 412become visible), then to displaying only the image portions contained inthe third partial region 806 (such that also the middle dots of thecolumns encompassed by the animation features become visible), and thento displaying all of the image portions contained in the fourth partialregion 808 (such that all of the animation features become visible).That is, in succession, the first, second, and third partial regions610, 804, and 806 are withdrawn and replaced by the second, third, andfourth partial regions 804, 806, and 808, respectively. In somecircumstances, such process of displaying and withdrawal of partialscreen information can be performed based upon, and/or varied (includingvariation in time) based upon, a variety of factors, for example,context, notification content, notification priority, or device state.

Finally, if the user has continued to touch the hit area (again, forexample, the first icon 404) continuously throughout the steps 906, 908and 910 all the way up to the beginning of the performing of the step912, then at the step 912 the fifth partial region 810 is displayed. Atthis point, the image displayed by the touch screen display 105 switchesfrom the peek animation image 410 of FIG. 4C to the peek view image 414of FIG. 4D, and the electronic device 100 is now operating in the peekview mode corresponding to the step 336 of FIG. 3. It will beappreciated that the particular manner of displaying the animationfeatures 412 the various steps 906, 908, and 910 particularly isintended to communicate (as a visual cue or hint) to the user that theuser can further complete an actuation in the peek view mode by movingthe user's finger from 512 from one of the icons 404, 406 to one of theicons 405, 407 shown in the peek view image 414. It also should beunderstood that, although the present discussion envisions that theuser's finger 512 maintains continuously the touching of the hit areaall of the time from the step 904 up to the step 912 so as to reach thepeek view mode, in other embodiments such touching need not be entirelyor substantially continuous.

Referring still to FIG. 9, once the step 912 and peek view mode havebeen reached, any of a number of different results can occur dependingupon how the user interacts with the touch screen display 105 while inthe peek view mode. In the present embodiment, interaction with thetouch screen display 105 in the peek view mode depends upon the user'sgestural behavior in view of the differences between the peek view image414 and the breathing view image 402 (and peek animation image 410) interms of the placement of the “hit areas”. In particular, in the presentexample embodiment, although the icons 404, 406 are considered to be thetouchable hit areas while the electronic device 100 is operating in thebreathing mode (for example, at the step 904), at the step 912 the hitareas change so as to encompass each of the icons 405 and 407 that arenow positioned toward the upper and lower ends of the touch screendisplay 105 in the peek view image 414. That said, in the presentembodiment, the user's manipulation of the user's finger 512 in relationto the icons 405 and 407 of the peek view image 512 determinegoing-forward operation.

More particularly, in this embodiment in which the relocated hit areasare the icons 405 and 407, user gestures by moving the user's finger 512produce the following results in peek view mode. First, as indicated atthe step 912 by a sub-step 914 and a sub-step 916, if the user holdstheir touch for a specific (“long”) amount of time (e.g., all of thetime between the step 902 and the step 912) and then, upon reaching thepeek view mode at the step 912, slides the finger 512 so as to reach theicons 407 and then further removes the finger from the touch screendisplay after doing so, then the process advances to a step 918. Thisresults in awakening of the electronic device 100, turning on of theprocessors 203, and launching of an intent corresponding to the icons407 (e.g., launching of an application). Thus, by virtue of the userselecting the icons (or one or more of those icons) 407, the electronicdevice 100 proceeds from the peek view mode within the intermediate modeto the fully awake mode.

Similarly, as further illustrated by the sub-step 914 and a sub-step920, if the user holds their touch for a specific (“long”) amount oftime and ultimately releases their touch after sliding the finger 512 tothe hit area corresponding to the icon 405 proximate the top of thetouch screen display 105, then a step 922 is performed at which theelectronic device 100 switches from the intermediate mode to the fullyawake mode and an intent corresponding to the icon 405 is launched.Thus, both with respect to the peek view mode operation resulting in theperforming of the step 918 and the peek view mode operation resulting inthe performing of the step 922, the actuation involves a sliding gestureportion corresponding to the arrows 515 already discussed with respectto FIG. 5D, where the user's finger 512 is manipulated so as to movefrom an original location corresponding to a breathing mode hit area(e.g., the icons 404, 406) to a peek view mode hit area (e.g., the icons405, 407).

It should be noted that, in the present example embodiment, in order toachieve the launching of an intent at either of the steps 918 or 922,the touch contact between the user's finger 512 and the touch screendisplay 105 must remain constant and continuous throughout the peek viewmode of operation, as the user's finger is moved from the location ofthe initial (breathing mode) hit area corresponding to one of the icons404, 406 to the final (peek view mode) hit area corresponding to one ormore of the icons 405, 407. Indeed, in the present embodiment, it isenvisioned that, to achieve the launching of an intent at either of thesteps 918 or 922, the user's finger needs to have been in constant andcontinuous contact with the touch screen display 105 all of the timebetween the step 904, at which the transition from breathing mode topeek view mode began, and the time at which the releasing of theappropriate hit area occurs in the peek view mode at either of the steps916 or 920. Yet such operation is merely one example type of gesturesintended to be encompassed herein, and the present disclosure isintended to encompass other types of gestures that do not entail suchuninterrupted, continuous contact between the user's finger 512 and thetouch screen display 512.

Further, in at least some embodiments, the launching of an intent atsteps such as the steps 918 and 922 is accompanied by haptic or othertypes of feedback, such as a buzzing/vibration of the phone, to alertthe user that the intent has been launched. Additionally, in at leastsome embodiments, the launching of the intent at the respective steps918 or 922 cannot proceed unless, subsequent to the corresponding userrelease steps (the steps 916 or 920, respectively), an unlockingoperation is performed at the electronic device. Such an unlockingoperation can involve receiving a further touch input from the user(e.g., touching of one of the image portions of the peek view screen 414or another image portion) signifying that the user wishes to unlock thedevice, so that further actions such as the launching of the intent canoccur. It should be appreciated that, although such unlocking operationcan be performed in regards to the steps 918 and 920, it is furtherintended that the present disclosure encompass additional embodiments inwhich unlocking or locking steps are performed at other times, such asin relation to one or more other steps of the processes described inrelation to FIGS. 3-10B herein.

In addition to the above manners of operation, additionally as shownwith respect to the step 912, several other results can occur ratherthan the launching of intents at the steps 918 and 922 if the user'sfinger 512 is not moved to (and released from) one of the hit areas ofthe peek view image 414 as discussed above but rather one or more otherevents occur. First, as indicated by a sub-step 928, in somecircumstances even after the peek view mode has been reached (e.g.,because the user's finger 512 has held the appropriate touch from thestep 904 up to the step 912) the electronic device 100 can be forced toawake for some reason, for example, due to a power button press asdiscussed above in relation to the step 330 (in some cases, such a powerbutton press can be an elongated press, such as a 5-second button press,which among other things can reset a newness counter). If this occurs,then the process advances from the sub-step 928 of the peek view modeagain to the fully active mode as shown at a sub-step 930, at which theelectronic device 100 is awakened and breathing mode operation isceased.

Further, additionally in some circumstances even after the peek viewmode has been reached (again, e.g., because the user holds the touch forthe specific amount of time as indicated by the sub-step 914, from thestep 904 to the beginning of the step 912), the user's finger 512 canleave the touch screen display 105 at a location that does notcorrespond to one of the hit areas in the peek view image 414 (that is,at a location not corresponding to any of the icons 405, 407). Dependingupon the location at which the user releases the touch in this manner,then the sub-step 914 proceeds to either a sub-step 924 or a sub-step926 as shown. More particularly, if the user releases the touch at alocation corresponding to the sub-step 926, then the process returnsback to the breathing mode as indicated by an arrow 927 leading from thestep 912 (and sub-step 926) back to the step 904.

Further, if the user releases the touch at a location not over the hitarea as indicated by a sub-step 924, it is also possible for the processto advance to a step 932, at which breathing mode (and peek view mode)operation is stopped and the most image displayed on the touch screendisplay associated with breathing mode/peek view mode operation is fadedout (e.g., the peek view image 414 is faded out). Upon the step 932being performed then the process further advances to a step 934, atwhich the dimensions of the partial region 610 are reduced so as toexclude notification content (in effect, the partial region 610 isreplaced by a different partial region smaller than the partial region610, which is not shown in FIG. 8B).

Additionally, the process subsequently advances to a step 936, at whicha user can initiate a new breath as a result of a device gesture 936.Finally, upon such a gesture being received at the step 936, then theprocess advances to a step 938, at which the electronic device 100enters an additional, special mode that can be referred to as aclock-only mode. As shown, in the clock-only mode, a gesture initiatedpeek view image 939 is displayed on the touch screen display 105. Insuch a view, the touch screen display 105 only displays afurther-reduced partial region 940 (mentioned already in relation to thestep 934) that has dimensions particularly suited for displaying onlythe time display 408. Such operation can also be considered to be a“privacy mode”, since less information/device is shown than is shown inother images such as the breathing view image 402 and peek view image414. Also, it should be noted that such operation can be reached uponlocking of the electronic device and, the content/information regardingnotifications in some such embodiments can only be viewed upon unlockingof the electronic device.

Although not shown in FIG. 9, it should be appreciated that, uponreaching the clock-only mode corresponding to the step 938, it ispossible for the electronic device 100 to return to at least one of theother modes such as the fully awake mode, intermediate mode, or offmode, in various manners. For example, the fully awake mode can bereached in one embodiment if a power button press such as that shown inthe step 330 occurs. Additionally, it should further be noticed fromFIG. 9 that, in the present embodiment, the electronic device 100 canreach the clock-only mode directly from the off mode rather than fromthe intermediate mode. More particularly as shown, upon beginningoperation at the off mode as indicated by a start indicator 940, theprocess can begin at a step 942 at which the electronic device 100 isnot breathing and the display screen is off, because there are no knownnotifications that need to be breathed. Notwithstanding this to be thecase, the process can further advance from the step 942 to the step 936in the event that the user initiates a new breath as a result of adevice gesture, as discussed above. When this occurs, as alreadydiscussed above, the process again can reach the clock-only mode of thestep 938.

Now turning to FIGS. 10A and 10B, further flow charts 1000 and 1050 areprovided that show additional example subprocesses that can be performedby the electronic device 100 of FIGS. 1 and 2, which can be consideredto be encompassed generally by the example process represented by theflow chart 300 of FIG. 3. The flow chart 1000 of FIG. 10A shows exampleadditional steps of operation in which the electronic device 100transitions between the breathing mode corresponding to the step 326 ofFIG. 3 and the off mode of the region 304 of FIG. 3. The flow chart 1050of FIG. 10B further shows example additional steps of operation in whichbreathing operation of the electronic device 100 in the breathing modevaries in response to gestures that are sensed by the electronic device,as well as further steps of operation in which particular breathingoperation can be triggered by a gesture even when the electronic device100 is otherwise in the off mode.

More particularly, the subprocess represented by the flow chart 1000 ofFIG. 10A begins, as indicated by a start indicator 1002, at a step 1004,at which the electronic device is operating in the breathing modebecause there are one or more notifications suitable for being breathed.Then, as indicated by a step 1006, at some point the user can place theelectronic device 100 into a face-down position. The electronic device100 by virtue of one or more of its sensors 228 can detect suchpositioning and, if the electronic device determines that it is in aface-down position in accordance with a step 1006, then the processadvances from the step 1004 via the step 1006 to a step 1008, at whichbreathing becomes stopped and there is no displaying at all of anyincoming notifications by way of the breathing mode process.

Further as shown, even if the electronic device 100 is not positioned ina face-down manner as determined at the step 1006, then the electronicdevice 100 can further determine, as represented by a step 1010, whetherthe electronic device has been “stowed” for a certain predeterminedamount of time (e.g., for X seconds). Depending upon the embodiment,when the electronic device 100 is “stowed” can depend upon a variety ofpossible environmental or operational circumstances, and can bedetermined upon a variety of input signals provided the sensors 228,including for example sensor input signals indicating that theelectronic device is within a confined region such as a user pocket, auser purse, or a drawer of a desk. If at the step 1010 it is determinedthat the electronic device 100 has been stowed for a predeterminedamount of time, then the process again advances to the step 1008, atwhich breathing operation is shut down. Alternatively, if it isdetermined at the step 1010 that the device has not been stowed for thepredetermined amount of time, then the process returns to the step 1004in which breathing operation continues.

Additionally as shown, upon the process reaching the step 1008 in FIG.10A, the electronic device 100 operates in an off mode during which nonotification messages of any kind are communicated to the user. That is,as illustrated by a step 1012, even if new notifications arrive duringthis off mode when the breathing is shut down, the receipt of such newnotifications neither results in the display of any notificationmessages, nor causes the breathing operation to begin again. Rather,even when such new notification messages arrive, the process stillreturns to the step 1008 at which breathing operation is shut down.

Although breathing operation does not commence upon the receipt of anynew notifications when the breathing operation is shut down at the step1008, the breathing operation can begin again if one or the other of theconditions that gave rise to the shutting off of the breathing operationno longer remain(s) true. That is, if as represented by a step 1014, theelectronic device 100 while in the off mode of the step 1008 continuesto determine that the electronic device is face down, the electronicdevice then remains in the off mode of the step 1008. However, if theelectronic device is not face down any longer as determined at the step1014, then the process advances to a step 1016, at which it is furtherdetermined whether it is true that the electronic device has been stowedfor the predetermined threshold (again, e.g., X seconds). If it is stilltrue that the device has been stowed for the predetermined threshold oftime, then the process continues to remain in the off mode of the step1008. However, if at the step 1016 it is determined that the electronicdevice has not been stowed for the predetermined threshold of time anylonger, then the process advances from the step 1016 to the step 1018,at which breathing operation is restarted and the process then returnsto the step 1004.

As indicated by the step 1018, the restarting of the breathing at thisjuncture can be performed in a particular manner in which there is anelongated initial plateau (elongated period of time at which there ismaximum intensity) for the first breath, after which normal breathingoperation proceeds. It should be appreciated that the subprocess of FIG.10A in which the face up/face down and stowing conditions are taken intoaccount in relation to the breathing operation is particularlyadvantageous in that, by stopping breathing when the device is stowed orface down, the chance of inadvertent triggering of the phone (e.g.,falsing) can be reduced. Although not shown in FIG. 10A, it should beappreciated that other conditions can also trigger breathing operationto be shut down. For example, in at least some embodiments, theelectronic device 100 can consider whether the current time is within arange corresponding to night-time/sleeping (e.g., 11 PM to 6 AM) and, ifso, can automatically shut off the breathing operation when thebeginning of that range occurs and automatically turn the breathingoperation back on when the end of that range is reached. Such operationcan be referred to “sleep mode” operation.

As for the subprocess shown in the additional flow chart 1050 of FIG.10B, as shown that subprocess can begin, as represented by a startindicator 1052, either with a step 1054 or a step 1056, where the step1054 constitutes ongoing operation of the electronic device 100 in thebreathing mode that is occurring because there are notifications tobreathe, and where the step 1056 constitutes operation of the electronicdevice in the off mode, during which the device is not breathing becausethere are no notifications that need to breathe. With respect to thestep 1054 in particular, it should be appreciated that this step isidentical to or can be considered to be identical to the step 1004 shownin FIG. 10A. That said, although not shown, it should therefore beunderstood that the particular process steps occurring in the FIG. 10Bbeginning with the step 1054 could equally proceed from the step 1004 ofFIG. 10A (and also that the particular process steps of the FIG. 10Acould flow from the step 1054 as well).

Further with respect to FIG. 10B, regardless of whether the subprocessbegins with the step 1054 or 1056, the subprocess can proceed fromeither of these steps based upon a determination by the electronicdevice 100 as to whether any movement of the electronic device has beendetected (e.g., by the sensors 228) for a predetermined amount of time.If, as indicated by a step 1058 following the step 1054, it isdetermined by the electronic device 100 that there has been movementdetected within a predetermined amount of time (e.g., within the past Xseconds), then the process continues to remain in the breathing mode andcontinues to cycle back from the step 1058 to the step 1054. Likewise,if at a step 1060 following the step 1056 it is determined by theelectronic device 100 that there has been movement detected within thepredetermined amount of time (e.g., within the past X seconds), then theprocess returns to and continues to cycle back to the step 1056 andremains in the off mode where breathing is not occurring.

Alternatively, if at either of the steps 1058 or 1060 it is determinedthat movement that the electronic device 100 has not been moved for aparticular amount of time, then the process instead advances from thestep 1058 to a step 1062 or from the step 1060 to a step 1064,respectively. At each of the steps 1062 and 1064, the electronic device100 becomes ready to receive a movement gesture, that is, a movementgesture is now armed. Notwithstanding the arming that occurs at thesteps 1062 and 1064, otherwise subsequent to these steps the electronicdevice 100 remains in the same state regarding breathing operation. Thatis, as illustrated, the process advances from the step 1062 to a step1066 at which ongoing breathing operation continues and in which theelectronic device 100 is waiting for additional movement (the movementgesture). Likewise, upon the step 1064 being performed, then that stepis followed by a step 1068 at which breathing operation remains off andthe electronic device is waiting for additional movement.

Subsequent to the steps 1066 and 1068, respectively, as indicated by astep 1070 and a step 1072, respectively, the electronic device 100 thendetermines whether any movement has now occurred for a new predeterminedthreshold (length amount) of time (e.g. for Y seconds), for example, byway of sensing performed by the sensors 228 (e.g., an accelerometer orGPS device). In the present embodiment, the electronic device 100 isconfigured to consider any detected movement as satisfying the steps1070, 1072 (even, for example, only a nudge or micromotion) albeit, inother embodiments, the electronic device 100 is configured so that onlythe detection of a movement of a particular type, extent, or magnitudewill satisfy one or both of the steps 1070, 1072. Additionally, althoughthe new predetermined threshold of time is shown in the steps 1070, 1072to be different than that of the steps 1058 and 1060, this need not bethe case. Indeed, any and all of the time thresholds discussed hereincan be varied depending upon the embodiment or circumstance.

That said, if no movement has been detected over the new predeterminedthreshold of time in the case of the step 1070, then the process returnsto the step 1066 in which ongoing breathing operation continues and theelectronic device continues to wait for a movement, and if no movementis detected over the new predetermined threshold at the step 1072, thenthat step returns to the step 1068 at which the breathing operationremains shut off and the electronic device continues to wait for amovement.

Alternatively, if movement is detected within the new predeterminedthreshold of time at the step 1070, then in that case the processadvances from the step 1072 to a 1074, at which breathing operation iscontinued but is restarted in a manner where there is an elongatedplateau for the first breath. That is, the time period of the breathingplateau at which the first breath is displayed with maximum intensitylengthened relative to a normal length of the plateau. After theperforming of the step 1074, the process then returns to the step 1054,and breathing operation continues on as normal. Further, if movement isdetected within the new predetermined threshold at the step 1072, thenthe process advances from the step 1072 to a step 1076, at which theelectronic device 100 causes the touch screen display 105 to display asingle breath within an elongated plateau and then, following thedisplay of that single breath, then the electronic device returns to thestep 1056 at which breathing operation is shut off.

Finally, also as shown in FIG. 10B, it should be noted that the portionsof the subprocess of the flow chart 1050 involving both ongoingbreathing operation and operation during which breathing is shut off arelinked insofar as, in each case, if a new notification arrives, thenbreathing can be restarted. More particularly in this regard, upon a newnotification arriving when the device is in the breathing mode at thestep 1054, then as indicated by a step 1078 the process proceeds to astep 1074, at which the breathing is restarted but with an elongatedplateau for the first breath, after which the process returns to thestep 1054. Likewise, upon a new notification arriving when the device isnot breathing as indicated by the step 1056, then as indicated by a step1080 the process also proceeds to the step 1074, at which the breathingis restarted (with an elongated plateau for the first breath), afterwhich the process also proceeds to the step 1054 in which breathingcontinues.

From the above discussion and description, it should be appreciated thatthe present disclosure encompasses numerous features and manners ofoperation, including among other things numerous features and manners ofoperation relating to the receipt and display of notifications. It isintended that the present disclosure encompass not only the particularembodiments described above, but also numerous other variations of thoseembodiments. Among other things, in at least some embodiments, the colorof touch screen display 105 (of the user interface screen), or portionsor aspects thereof, such as a backplate or wall paper color, can bevaried. This can impact numerous aspects of operation, such as forexample the color of the clock in the time display 812. Also forexample, if notifications are to be prioritized in some manner orcertain notifications are of high priority for a particular reason(e.g., because the notifications come from particular persons who areidentified as favorites in the user's contact list), then thosenotifications or portions thereof (e.g., the name of the personindicated in the notification) can be displayed or highlighted in aparticular color or colors.

Among other things, at least some embodiments encompassed herein includefunctionality in which the processors (e.g., application processors) ofthe electronic device are awake and awakened in some circumstances bythe receipt of new notifications. When awake, the electronic device canturn on the display screen to display such a notification or to providea full-screen alert about such a notification that remains on screen fora pre-defined amount of time. Further, in some such embodiments, oncethe pre-defined amount of time has elapsed, the display turns off andsensor hub regains control of the display. When under the control of thesensor hub, a partial region of the display may turn on and off atspecific times, a process that can be referred to as breathingoperation. Breathing patterns can vary over time and based on context,notification content, notification priority, or device state.

Further, in at least some embodiments, even though the electronic deviceis under the control of the sensor hub (in a low-power mode of operationsuch as the breathing mode), a wake event can be detected that willcause the processors (application processors) to awaken. Such triggeringevents can include the receiving of any of many inputs, including butnot limited to: a button press, an on-screen touch event or gesture.Further, in at least some embodiments, upon awakening, the electronicdevice can cause a special “Landing Screen” or other default screen tobe displayed on the touch screen display, which can be a single point ofentry upon waking of the device. From the Landing Screen, the user cantake actions on individual notifications, individual applications, orperform a general unlock request.

Additionally, in at least some embodiments when such a Landing Screen(or other default screen) appears, as well as when subsequent screensappear in response to user inputs (e.g., user touching of a userinterface element with the user's finger or a stylus), a consistentmethod of interaction can be employed. For example, in some embodiments,when a user touches on an icon from within the Landing Screen, this willresult in multiple hit areas appearing, and unnecessary user interfaceelements will also disappear. Also, in some embodiments, the user mustretain continuous touch on the display to remain in a given mode. If theuser removes the user's finger from the touch screen display beforereaching a hit area, the given mode is exited. Also, in at least someembodiments, as long as the touch input remains distant from the hittarget, the user interface elements surrounding the hit target shouldhave no opacity (and thus there will be no visible surrounding userelements).

Further, in at least some embodiments, as the touch input approaches ahit target, the user interface elements surrounding the hit target thatis being approached should increase in opacity and/or increase in sizeand/or increase in quantity and, just before the touch input reaches thehit target, the area surrounding the hit target should have increased tofull opacity and/or full size and/or full quantity. Additionally, in atleast some such embodiments, once the touch input reaches the hittarget, the hit target can be displayed with a highlight, indicatingthat the hit target has been reached. Further, upon the user's releasingof the touch while within the hit area, the resulting action shouldincluding performing of the action associated with the hit area (forexample, exiting of a locked screen, opening of a specific application,or the taking of a specific action associated with a particularnotification).

Additionally, in at least some embodiments, if the touch input is notreleased while within (or at or sufficiently proximate to) a hit target,but instead is moved away from the hit target, the hit target should nolonger be highlighted, and the area surrounding the hit target shoulddecrease in opacity as the touch input moves further away from the hittarget. Further, if the touch input is released when a hit target is notreached, the interface should return to displaying the Landing Screen orother default screen. It should be noted that, with respect to the hitareas, in at least some embodiments these can take any of a variety offorms and, in at least some embodiments, these are larger than thevisible icons.

Further, in at least some embodiments, incoming notifications (orincoming alerts) are prioritized according to various factors, including(but not limited to) context, user preference, learned behaviors, numberof notifications, type of notifications, device state, and source ofnotification. Additionally, in some embodiments, a particular incomingalert or notification should be displayed only if it has met thecriteria as determined by the prioritization rules. By virtue of suchprioritization, only the most relevant notifications can be shown.

Also, in some embodiments, an Incoming Alert screen can be providedhaving certain (e.g., limited) functionality, in order to allow the userto take action on notifications as soon as the notifications aredisplayed. In such embodiments, if user touches on the Incoming Alertscreen with the intention to act on the notification, but then releasestouch without reaching a hit target, the interface will return to adefault screen such as the Landing Screen.

Further, in at least some embodiments, the electronic device is capableof any of a variety of states, modes, or levels of operation. In someembodiments, there are three (3) levels (or three primary or corelevels) of interaction between user and device, namely: (1) an activelevel or mode during which the user is in possession of device, and isregularly using it or looking at the screen often; (2) a nearby level ormode during which the electronic device is near the user, but determinesit is not the primary method of interaction (with the user) at aparticular time; and (3) an asleep level or mode that arises as a resultof the electronic device determining that the user is sleeping. In somesuch embodiments, each of the levels of interaction will result indifferent breathing patterns and display brightness. For example, in oneexample embodiment, operation in the active level is such that, during abreathing cycle, the display may remain on longer (and off shorter) inorder to ensure the user notices the breathing state as often aspossible. Also, in such an embodiment, during operation in the nearbylevel, the breathing cycle will be longer than during operation in theactive level, but the display will remain off longer. Further, in suchan embodiment, during operation in the asleep level, the breathing cyclewill be very minimal (and can be disabled entirely), and displaybrightness will be very low (for example, ˜10 nits), so the user is notbothered while trying to sleep. Further, in some such embodiments,display brightness during the breathing states can also be influenced byinput from an ambient light sensor.

Further, in at least some embodiments, there are several device statesthat can trigger different experiences. For example, if the electronicdevice is face down on a flat surface, this can trigger disabling of thebreathing and incoming alert screen until this state is no longeractive. Also for example, if the electronic device is stowed (e.g.,within a pocket, backpack, etc.), this can trigger disabling of thebreathing and incoming alert screen until this state is no longeractive. Further for example, if the electronic device is face up on aflat surface, the electronic device in this state can generally behaveas normal, but can further start a timer to trigger a “Nudge” (e.g., amessage to the user to take some action) at a future time. And, upon aNudge occurring (while face up on flat surface), this can result inwaking of the device or resetting of the breathing pattern.

The present disclosure further encompasses numerous different manners ofoperation in different types of breathing modes that are possibledepending upon the embodiment and/or depending upon a variety offactors. In at least some embodiments, the electronic device is able, inresponse to a new alert, to transition to an Urgent Breathing Stateafter a specific amount of time, and then to transition further to aNormal Breathing State after another specific amount of time. Also, inat least some embodiments, while the electronic device is in a breathingstate, the device will wake up when user input is detected. Such userinput can be detected through various methods, including (but notlimited to), occurrences of a button press, an on-screen touch event, orgestures. In at least some embodiments, a user can touch on a userinterface element associated with any notification to take action on thecorresponding notification intents.

In at least some embodiments, notifications that are determined to behighly relevant are particularly exposed in the Urgent Breathing state,with the user interface displaying an indicator for which notificationis highlighted in the Urgent Breathing Stage (in other embodiments, suchan indicator need not be provided). When such indication is provided, auser can touch on the highly relevant notification (or any othernotification) to take action on the corresponding notification intents.Over time, if a notification previously deemed highly relevant isdetermined to no longer be as highly relevant, the Urgent BreathingState can transition to a Normal Breathing State. In some embodiments,Highly Relevant information can also displayed on a default screen suchas the Landing Screen.

In at least some additional embodiments, touch inputs can be receivedduring an AoD (Always-on Display) mode, which can also entail a partialdisplay mode and/or a breathing mode or state of operation. In some suchembodiments, error detection and falsing prevention will help eliminateunintentional wakes. Further, if a touch input is detected during thismode, the device will wake up and, if an appropriate continuous touchinput is detected arising from the breathing mode, the device will wakeup and handle the touch event accordingly. In particular, if acontinuous touch input is detected over a specific hit area, this willresult in a cohesive experience from the “off” screen state or breathingmode all the way to the Landing Screen, and into the detail forwhichever notification was selected by the user. Once this has occurred,the user will be able to act on the notification. This is allaccomplished with a single touch from the user. In at least some furtherembodiments, there will be visual, haptic, and potentially auditoryfeedback to help communicate what is happening to the user. Also, in atleast some embodiments user interface transitions between each of thevarious modes or states during a continuous touch will be smooth,responsive, and appear to be a single action.

Depending upon the embodiment, there are various types of content orinformation that can be shown during a breathing mode of operation, anyof which can be shown alone or with additional content during thebreathing mode. Some such example types of content can include: DeadBattery Charging (Sign of Life) Mode; Normal Charging Mode; Low BatteryWarning Mode; Contextually-driven advertisements; map navigationinformation (such as that provided by Google Maps, available fromGoogle, Inc. of Mountain View, Calif.); music controls; and contextualalerts and notifications.

Also, in at least some embodiments, while the electronic device displayis (or application processors are) off, operation in the breathing modecan proceed during which an image is faded in and out on the displayscreen. Such display operation particularly can include attributes suchas: a first attribute in which there is a delay at start of thebreathing cycle (this delay can be, for example, 3000 ms in length, orany other value); a second attribute in which there is ramping up of thedisplay over a period of time (for example, 1000 ms); a third attributein which the display brightness is at a maximum value or plateau for anadditional period of time (for example, 1000 ms); a fourth attribute inwhich the display brightness is ramped down over another period of time(again, for example, 1000 ms); and a fifth attribute in which thedisplay is off for a further period of time (for example, 5000 ms). Interms of the maximum brightness occurring during the plateau, this canbe set to any of a variety of values including, for example, a “100%”setting. The ramping up and ramping down can be linear, logarithmic,sinusoidal, in accordance with some other curve and/or some other typeof functional relationship. Breathing state attributes can varydepending on context.

Additionally, in some embodiments, the electronic device provides a lockscreen, and during display of this scree the user can touch on a userinterface element associated with a specific notification to displayactions and additional details and images associated with thisnotification. In some such embodiments, when the user touches on a userinterface element associated with a notifications, two actions can bedisplayed, or alternatively more than two actions can be displayed,depending on the notification content and what contextually-relevantactions are available for that notification. In some such embodiments,at a minimum, one of the actions associated with notification shouldhave the ability to dismiss the notification from the Landing Screen (orother default screen), Breathing State, and/or across the system.Further, when an action or intent is selected by the user, thatparticular action or intent will be taken, and the notification will bedismissed, it being understood that actions or intents can encompass orinclude (but are not limited to) any of a variety ofapplication-requested actions, or new actions that are contextuallyrelevant to the notification.

Further, in at least some such embodiments, if a lock method is in place(including but not limited to PIN, Password, Pattern, and Face Unlock),the lock method user interface will be displayed when the user takesaction on a particular notification. Upon successfully unlocking, theintended action will be taken. If the action is not completed (becauseunlock was not successful), the associated notification will not bedismissed until acted upon or specifically dismissed from the LandingScreen (or other default screen). Also, the electronic device will beable to display notification details and images without requiring anunlock, in order to allow the user to view and dismiss such notificationwithout unlocking first.

In at least some embodiments in which an application passesuser-specific identifier(s) along with a notification, then additionalcontextual actions can be displayed within the user interface. This willallow additional actions that are contact-specific, rather thannotification-specific (e.g., allow the user to respond to a Text Messagewith an Instant Message, or allow user to call the organizer of ameeting that is being shown on the screen).

In addition to the above discussion, in at least some embodiments, thepresent disclosure relates to a user interface that appears when anelectronic device display is considered ‘off’ to the user (but stillcontrolled by the sensor hub), as well as the user interface andfunctionality that supports it. In such embodiments, incomingnotifications are normally displayed and also a breathing mode or statecan be entered, in which limited notification information is displayedon an occasional, or periodic, basis.

In at least some embodiments, a lockscreen widget plays a role inimplementing lockscreen behaviors and interactions. Such a lockscreenwidget can take a variety forms, including smaller and larger widgets(that occupy smaller or larger portions of the display of the electronicdevice), which can appear for example in response to user swiping orfrom a breathing screen. In some such embodiments, the lockscreen widgetparticularly is an icon or displayed image portion that is reflective ofinformation concerning one or more new notifications that have beenreceived but have not yet been reviewed by a user (also, in some suchembodiments, the lockscreen widget can show related information, such asan image of a third party by whom the notification was sent). In somesuch embodiments, the lockscreen widget is an item that can be selected(e.g., by way of a touch input) by a user to unlock the electronicdevice so as to allow for viewing of the notification. In some suchembodiments an unlocking region is also displayed so that a user canconfirm an action that was taken.

Further in at least some embodiments, breathing operation only occurs ifone or more notifications of a certain priority level (e.g., a priorityof zero or above) are present (have been received by the electronicdevice) and have not yet been seen by the user. If the user opens alockscreen widget or a notification dropdown, breathing should bestopped (however, if a different sized lockscreen widget, e.g., asmaller widget, is being displayed, then breathing will not be stopped).Even after display of notifications, breathing can resume as soon as anew notification of appropriate priority (e.g., priority 0 or above)occurs.

In at least some further embodiments, breathing content can followparticular rules (not immediately after the incoming screen). First, anotification shown on a breathing screen should be filtered by newness,so that only new notifications (since the last breathing “stop”) will becandidates for the breathing screen. Second, the notification shown onthe breathing screen can be sorted first by score, and then by time, andthe notification with the highest score can be shown on breathingscreen. If multiple notifications have the same highest score, thenthose notifications can be further sorted by time, such that the highestscored, most recent notification is shown.

Further, in at least some embodiments, if breathing has been stopped,and a new notification comes in, the following will happen. First, theincoming screen is shown, and then after a time out breathing operationbegins. Further, the breathing state should show any new notificationthat just arrived. If multiple notifications occur before the user wakesthe device and (if applicable) opens a locking screen widget asdescribed above or opens a notification dropdown, then the most recenthighly rated notification should be shown. If the user wakes up thedevice, the notification that had been breathing should be the one thatis shown on the locking screen widget. Further, if the widget that wasshown on the breathing screen concerned a latter one of severalnotifications (e.g., 5th out of 7 notifications), then the lockingwidget should show the notification in the 5th position in order of allnotifications (so clicking the previous button would go to the 4thnotification, and clicking next would go to the 6th notification).

In at least some such embodiments, the notifications can be handled orprioritized in a variety of manners. For example, in some embodiments,the electronic device 100 can: ignore all notifications that are toggledON in a blacklist; ignore all ongoing notifications; ignore allnotification with a low or negative score (e.g., a score below 0);ignore all notifications that had occurred before the last time the userviewed a lockscreen widget; ignore all notifications that had occurredbefore the last time user showed curtain view.

Also, in some embodiments, various display features and rules fordisplaying features are provided. For example, a row of icons shown inthe top of the screen can be the same as the icons shown in a statusbar. Further, in some embodiments, when a notification clear occurs atbackground, the breathing view should be updated. Among other things,the row of icons at top of screen needs to be updated. Also, if thebreathing notification is the one to remove, then the process can beginbreathing the next one that meets the proper criteria for breathing.Further, in at least some embodiments, in accordance with an IncomingView, the electronic device operates to: ignore all ongoingnotifications; ignore all notifications that are toggled ON in theblacklist; and/or ignore all notification with a low or negative score(e.g., a score below 0).

Additionally, with respect to lockscreen widgets, small or large widgets(e.g., 4×1 and 4×4 widgets, respectively) continue to reflect the orderand content of the notification dropdown. Notifications will not bedismissed or hidden without the user specifically dismissing them.Further with respect to such widgets, in determining whether to displaythese, the electronic device can: ignore all ongoing notifications;ignore all notification with a low or negative score (e.g., a scorebelow 0); and/or ignore all notifications that are toggled ON in theblacklist. Additionally, it should be appreciated that some packageswill be ignored by default, and thus pre-populated in a blacklist. Insome embodiments, the user will be allowed to manually add/remove itemsfrom the blacklist via the user interface (e.g., via accessing settingsoptions). Further with respect to Incoming Alerts, in at least someembodiments, a particular incoming alert or notification should bedisplayed only if it has met one or more criteria, such as thosediscussed above. The Incoming Alert screen can have limitedfunctionality, in order to allow the user to take action on suchnotification as soon as it is displayed.

Further, at least some embodiments of the present disclosure envisionthat partial displays are output by the display screen of the electronicdevice. In some such embodiments, a particular notification should beshown on the partial display ‘breathing’ state only if it has met one ormore criteria, such as those discussed above. The breathing state willhave limited functionality, in order to eliminate falsing while stillallowing lockscreen and widget functionality to be surfaced in this‘always on’state. While under control of the sensor hub, the electronicdevice can change the partial display regions or sequence of suchregions that are being displayed, depending on user interaction (e.g.,touch interactions or gestures). Display brightness during the breathingstates will be influenced by Ambient Light Sensor input.

Depending upon the embodiment, several device states can triggerdifferent experiences. For example, if the electronic device is facedown on flat surface, then the electronic device will disable breathingand incoming alert screen until this state is no longer active. Also forexample, if the electronic device is stowed (e.g., in a pocket,backpack, etc.), then the electronic device will disable breathing andincoming alert screen until this state is no longer active. Further forexample, if the electronic device is no longer face down or stowed, thenthe breathing pattern can be restarted immediately. In some embodiments,touch input will be possible from the AoD (Always-On Display, and/orpartial display and/or breathing modes). Further, in some embodiments,error detection and falsing prevention will help eliminate unintentionalwakes. Additionally, in some embodiments, user interface transitionsbetween each of various states during the continuous touch will besmooth, responsive, and appear to be a single action.

There are various types of content or information that can be shown in abreathing state. For example, the following types of content orinformation can be displayed alone or in combination with additionalcontent: dead battery charging (sign of life) mode; normal chargingmode; low battery warning mode; and/or contextual alerts andnotifications. Also, while the device display is off and in thebreathing state, breathing operation includes fading an image on thescreen in and out. Depending upon the embodiment the electronic devicecan have any number of different breathing states that have variousattributes, such as (for example): a first attribute at which there is adelay at the start of breathing cycle, which could be set to any value;a second attribute involving ramping up of the display brightness over atime period (for example, 1875 milliseconds (ms)); a third attribute atwhich the display is at a maximum brightness or plateau (for example,250 ms), where the maximum brightness can take on any value dependingupon the embodiment (for example, approximately 150 nits) and depend onambient light as well; a fourth attribute involving ramping down of thedisplay brightness over a time period (for example, 1875 ms), but couldbe set to any value; a fourth attribute at which the display is shut off(dark) over another time period (e.g., 7 seconds). These attributes canbe repeated in a looping indefinitely. Also, the ramping up and down canbe in accordance with linear, logarithmic, sinusoidal or other animationtypes, and breathing state attributes can vary depending on variousfactors, including (but not limited to) ambient light, gesture, andsmart action triggers.

While the preferred embodiments of the invention have been illustratedand described, it is to be understood that the invention is not solimited. Numerous modifications, changes, variations, substitutions andequivalents will occur to those skilled in the art without departingfrom the spirit and scope of the present invention as defined by theappended claims. Thus, it is specifically intended that the presentinvention not be limited to the embodiments and illustrations containedherein, but include modified forms of those embodiments includingportions of the embodiments and combinations of elements of differentembodiments as come within the scope of the following claims.

What is claimed is:
 1. A method comprising: while an electronic deviceoperates in a higher-power mode of operation: controlling, by at leastone application processor of the electronic device, and while consuminga first amount of power, a display of the electronic device to presentan image of a notification; and transitioning, by the at least oneapplication processor of the electronic device, from operating theelectronic device in a higher-power mode of operation to operating theelectronic device in a lower-power mode of operation; while theelectronic device operates in the lower-power mode of operation:controlling, by a sensor hub of the electronic device, independent ofthe at least one application processor and while consuming a secondamount of power that is less than the first amount of power, the displayto present a portion of the image of the notification; responsive todetermining that a condition of the electronic device is met,transitioning, by the sensor hub, independent of the at least oneapplication processor, from operating the electronic device in thelower-power mode of operation to operating the electronic device in anoff-mode of operation; while the electronic device operates in theoff-mode of operation: controlling, by the sensor hub, independent ofthe at least one application processor and while consuming a thirdamount of power that is less than the second amount of power, thedisplay so as to cease presenting the portion of the image of thenotification; responsive to determining that the condition of theelectronic device is no longer met, transitioning, by the sensor hub,independent of the at least one application processor, from operatingthe electronic device in the off-mode to operating the electronic devicein the lower-power mode to resume controlling, independent of the atleast one application processor, the display to present the portion ofthe image of the notification.
 2. The method of claim 1, furthercomprising determining, by the sensor hub, independent of the at leastone application processor, that the condition is met in response todetermining that the electronic device has been stowed within a confinedregion.
 3. The method of claim 2, wherein the confined region isselected from the group consisting of a pocket, a purse, a backpack, anda drawer.
 4. The method of claim 1, further comprising determining, bythe sensor hub, independent of the at least one application processor,that the condition is met in response to determining that the electronicdevice is face down on a surface.
 5. The method of claim 1, whereincontrolling the display to present the portion of the image of thenotification comprises: actuating, by the sensor hub, independent of theat least one application processor, the display using the at least onecontrol signal provided by the sensor hub, so that the portion of theimage of the notification is displayed in a periodic manner in whichportion of the image of the notification alternates between having ahigher level of brightness and a lower level of brightness.
 6. Themethod of claim 5, wherein the higher level of brightness include aplurality of plateaus during which there is the maximum intensitydisplaying of the portion of the image of the notification.
 7. Themethod of claim 1, further comprising: while the electronic deviceoperates in the lower-power mode of operation: receiving, by the sensorhub, independent of the at least one application processor, a signalindicative of a user input corresponding to the portion of the image ofthe notification; and responsive to receiving the signal, taking, by thesensor hub, independent of the at least one application processor, atleast one action.
 8. An electronic device comprising: a displayconfigured to present information; an application processor incommunication with the display, the application processor beingconfigured to: while the electronic device operates in a higher-powermode of operation: control, while consuming a first amount of power, thedisplay to present a notification; and transition, from operating theelectronic device in a higher-power mode of operation to operating theelectronic device in a lower-power mode of operation; and a sensor hubin communication with the display, the sensor hub being configured to:while the electronic device operates in the lower-power mode ofoperation: control, by the sensor hub, independent of the applicationprocessor and while consuming a second amount of power that is less thanthe first amount of power, the display to present an image portion ofthe notification; responsive to determining that a condition of theelectronic device is met, transition, by the sensor hub, independent ofthe application processor, from operating the electronic device in thelower-power mode of operation to operating the electronic device in anoff-mode of operation; while the electronic device operates in theoff-mode of operation: control, by the sensor hub, independent of theapplication processor and while consuming a third amount of power thatis less than the second amount of power, the display so as to ceasepresenting the image portion of the notification; responsive todetermining that the condition of the electronic device is no longermet, transition, by the sensor hub, independent of the applicationprocessor, from operating the electronic device in the off-mode tooperating the electronic device in the lower-power mode to resumecontrolling, by the sensor hub, independent of the applicationprocessor, the display to present the image portion of the notification.9. The electronic device of claim 8, wherein the electronic device is amobile device.
 10. The electronic device of claim 9, further comprisinga sensor configured to detect that the electronic device is stowedwithin a confined region, and the sensor hub is further configured todetermine, independent of the application processor and using thesensor, that the condition is met in response to determining that theelectronic device has been stowed within the confined region.
 11. Theelectronic device of claim 10, wherein the confined region is a pocket.12. The electronic device of claim 9, further comprising a sensorconfigured to detect that the electronic device is face down in relationto a surface, and the sensor hub is further configured to determine,independent of the application processor and using the sensor, that thecondition is met in response to determining that the electronic deviceis face down in relation to the surface.